Linus Unnebäck
Linus Unnebäck
Doesn't the same reordering happen if you run `npm install foo`? I think that this is intentional so that to commits adding two different dependencies won't create a merge conflict...
As it is currently designed, `npm-check` delegates the installation to your package manager, e.g. `npm`. It is then `npm` that reorders the dependencies and not this package. This makes it...
> Because the order of the keys in package.json has been changed, git diff thinks that a lot of code has been modified. True, but this will only happen one...
> What's preventing this PR from being merged ?
> PS: non maintainers / author of the PR can't see what the conflicts are, so it's good you joined that screenshot Did not know that, thanks for telling me!...
added in #75
Closing since it hasn't been anything happening for a few years, happy to reopen if someone wants to work on this...
added in #75
Merged in #75
Released in [v13.0.0](https://github.com/standard/eslint-config-standard-react/releases/tag/v13.0.0)