Hack in a package.yaml instead of package.json
json is just incredibly tedious to use for this, especially because of lack of comments. Upstream has been informed of this many times apparently, npm won't change it. Just hack it downstream. npm will never get better, will it...
This commit is contained in:
parent
f9bd128a02
commit
594e9bcbfd
10 changed files with 446 additions and 108 deletions
13
README.md
13
README.md
|
|
@ -4,12 +4,15 @@ Website templates bundled with parcel.
|
|||
|
||||
## Updating
|
||||
|
||||
When adding/removing packages from `package.json`, the corresponding
|
||||
`package-lock.json` needs to be updated. Use `nix/update-lockfile` for
|
||||
this.
|
||||
When adding/removing packages from `package.yaml`, the corresponding
|
||||
`package.json` and `package-lock.json` need to be updated. Use:
|
||||
|
||||
```console
|
||||
nix run .#update-lockfile
|
||||
```
|
||||
|
||||
When ignoring semver is desired, use:
|
||||
|
||||
```sh
|
||||
npm-check-updates -u
|
||||
```console
|
||||
nix run .#update-lockfile -- --ignore-semver
|
||||
```
|
||||
|
|
|
|||
Reference in a new issue