pomerium / pomerium/documentation
chore: Move from yarn to npm
Open
Nobody has claimed this yet.
Chore
- Dominant language
- MDX
- Stars
- 13
- Forks
- 23
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 11
Description
Spoke with @rjbeers about this. yarn 1.22 is very old and newer version of yarn aren't really used in frontend projects. Typically npm or pnpm is used these days. Let's move to standard npm. So we'll remove the yarn.lock file and commit the package-lock.json once npm install is run. Also, we should add yarn.lock to the .gitignore
Contributor guide
No contributing guide indexed for this repository
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
Start by checking yarn.lock, package.json, and .gitignore, then run npm install to see the generated dependency lockfile. Done means yarn.lock is removed, package-lock.json is committed, and yarn.lock is ignored.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- build-system, tooling
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 38/100