Making ts-standard easier to use

[standard]

Making ts-standard easier to use

[feross]

also there is no standard organization on npm

Our organization on npm is called standardjs because standard is being used by someone with private packages.

If you're keen to work on these issues, I'd love to solve it in standard-engine (where that makes sense) so that all downstream packages like standard, semistandard, ts-standard, etc. benefit and maybe we can close standard/standard#1356 at the same time!

[toddbluhm]

@divlo Thanks for the feedback. Initially, my goal for this package was to mimick standard as close as possible and keep feature parity with standard. However, your right, it looks like @feross is trying to improve the ease of use of standard

I'd say go for it! It might be cool to have this package be a test-bed for new standard features.

Make sure all new features are behind some sort of flag and opt-in only. All existing standard flags should continue to perform exactly like the regular standard that way we maintain full parity/backward compatibility with it.

[theoludwig]

Any thoughts ? @toddbluhm

[theoludwig]

Alright, I will try to open a pull request to add the --format flag to the CLI. 👍

I just cloned the repo but when I run npm run lint, I've got errors thrown by tsc --noEmit command, so I will first open a PR (see #104) to update dependencies and try to fix this issue, maybe once this is fixed, we could release the v10 release (also there is no standard organization on npm) before adding --format flag.