The package.json thing in git

Hey,

for some reason, npm upgrade is touching my package.json on every run.
This file is in git, so it is annoying to have that edited every run.
Can we do something with this?

···

--
Later,
  Lukas @lzap Zapletal

I think you're supposed to use npm install. npm upgrade is an alias for npm update (don't get me started that there's also the hardcoded udpate alias). npm update updates a package.

···

On Thu, Dec 14, 2017 at 04:18:45PM +0100, Lukas Zapletal wrote:

for some reason, npm upgrade is touching my package.json on every run.
This file is in git, so it is annoying to have that edited every run.
Can we do something with this?

I have this aliases:

alias bi="bundle install && test -f package.json && npm install ||
node_modules/.bin/npm install"
alias bu="bundle update && test -f package.json && npm upgrade ||
node_modules/.bin/npm upgrade"

We don't have Gemfile.lock in git, therefore update needs to be
executed often. I guess it does not apply to npm. Confusing.

···

On Thu, Dec 14, 2017 at 4:24 PM, Ewoud Kohl van Wijngaarden <ewoud@kohlvanwijngaarden.nl> wrote:

On Thu, Dec 14, 2017 at 04:18:45PM +0100, Lukas Zapletal wrote:

for some reason, npm upgrade is touching my package.json on every run.
This file is in git, so it is annoying to have that edited every run.
Can we do something with this?

I think you're supposed to use npm install. npm upgrade is an alias for npm
update (don't get me started that there's also the hardcoded udpate alias).
npm update updates a package.

--
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Later,
  Lukas @lzap Zapletal