Move from standard to neostandard
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 51
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
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).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the neostandard project and standard/standard#1948 for the proposed migration and the CLI dependency described here. First verify that a self-contained neostandard CLI is available; done means the project can move from standard to neostandard without relying on the unresolved external pull request.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100