Post-1.0?

[strager]

What should we do after releasing version 1.0?

Some ideas:

• TypeScript (Parse TypeScript syntax #690)
• JSX (Parse JSX (React syntax) #493)
• translations into other human languages
• new bug-finding rules
• JS embedded in HTML (Lint JavaScript within HTML #116) or Markdown (Lint JavaScript within Markdown #117)
• more editor plugins
• automated fixes (Suggest fixes for common mistakes #115)
• better error messages for parse errors

Which ideas we pursue will likely depend on feedback.

[singalhimanshu]

I think automated fixes will be really helpful for the new programmers to get a hint about how to fix the reported error.

[juancarlospaco]

Public documented C API to use it as a library too,
even a basic one to call it with a string argument.

[strager]

Public documented C API to use it as a library too,
even a basic one to call it with a string argument.

What is your use case?

[juancarlospaco]

Use it as a library, instead of calling it as a subprocess, which is slower and not so elegant.

[strager]

Use it as a library, instead of calling it as a subprocess, which is slower and not so elegant.

What application are you building which needs to integrate with quick-lint-js?

[KasonBraley]

Up-voting for TypeScript and JSX support

[tmcdos]

Plugin for PhpStorm and/or WebStorm - to replace the built-in ESLint checker/inspector.

[ffurger]

Just came across your quick-lint-js.

I wish I could install it as an extension in Nova, the next generation code editor in the Mac designed by Panic.

[strager]

I wish I could install it as an extension in Nova, the next generation code editor in the Mac designed by Panic.

I filed #590 for Nova.

[strager]

JSX support was added in version 2.0.0 (#493).

I filed #690 for TypeScript support. That'll be the major feature for 3.0.0.