license, integrity, resolved changing unexpectedly in package-lock.json

[dcheckoway]

Hello! Is there a command line option to force npm install to set license on entries in package-lock.json? Here's the sitch...

I just "promoted" an inherited dependency to a direct dependency. npm install [email protected] After running that, my package-lock.json was modified in a couple of ways I didn't expect:

• the license attribute disappeared
• it added integrity and resolved attributes

This is pretty consistent for any dependency changes I make. It feels as if I'm using a different version of npm than whoever on my team last modified dependencies.

I couldn't find anything in the docs about how to control this behavior. Not a big deal, just seemed odd. Can you help me understand what I'm missing, why these attributes would change?

Thanks in advance!