search

Level / community

Discussion, support and common information for projects in the community.
MIT License
42 stars 15 forks source link

Move from standard to neostandard #136

Open vweevers opened 2 months ago

vweevers commented 2 months ago

See neostandard and context.

I'll have to get over my dislike of dangling comma's and I will, because the point of a code style is to avoid bikeshedding. That's the main strength of standard, so let's align with the kind folks who are keeping it alive.

I do want to wait for a self-contained CLI to become available (https://github.com/neostandard/neostandard/pull/2) because I agree with https://github.com/neostandard/neostandard/pull/2#issuecomment-2135446338 and we're not really blocked here (standard works fine if you don't use typescript).

voxpelli commented 2 months ago

Another vote for https://github.com/neostandard/neostandard/issues/79 I see

Not sure when we will get a CLI solution, I do want to look into aligning that with ESLint and eg xo, especially to avoid having to release custom editor integrations https://github.com/neostandard/neostandard/issues/33

Feedback etc is welcome 🙏