You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 25, 2021. It is now read-only.
Your Library Usage page has sample code that no longer works, I think. The linter options now have to include a mandatory 'fix' flag, so the declaration of 'options' should look like:
Also as far as I can work out the code on the page won't work directly with node.js, which doesn't (yet) recognize the ES6 'import' syntax. This in spite of a title that says 'Using TSLint as a Node.js library'.
Can I politely suggest that it might be better to have JavaScript code that will run immediately with node here, rather than or as well as the TypeScript/ES6? It would save everyone having to edit it or transpile it to run it.
I'm happy to raise a PR for these if you like.
The text was updated successfully, but these errors were encountered:
* Fix sample code for recent changes, show ES5 JavaScript code that will run with node (#2768)
* Fixes requested: no console.log, consistent use of spaces, boolean flag not literal
Your Library Usage page has sample code that no longer works, I think. The linter options now have to include a mandatory 'fix' flag, so the declaration of 'options' should look like:
const options = { fix: false, formatter: "json", rulesDirectory: "customRules/", formattersDirectory: "customFormatters/" };
Also as far as I can work out the code on the page won't work directly with node.js, which doesn't (yet) recognize the ES6 'import' syntax. This in spite of a title that says 'Using TSLint as a Node.js library'.
Can I politely suggest that it might be better to have JavaScript code that will run immediately with node here, rather than or as well as the TypeScript/ES6? It would save everyone having to edit it or transpile it to run it.
I'm happy to raise a PR for these if you like.
The text was updated successfully, but these errors were encountered: