Open RickButler opened 6 years ago
Yeah, using latest/latest LTS is a good idea.
Also, I wouldn't worry too much about overwriting the package-lock.json file. I've had no issues between differences in package-lock file across versions of npm, on any of my repos.
I was going to do a minor patch for the memory leak in _subviews, and I have npm
@latest
(6.1.0) and rannpm install
and it overwrote the package-lock.json. It seems like they have made a lot of changes between certain NPM versions. For some context and history see this stackoverflowI was thinking we should either always use
@lastest
or we should be using the newest version released as part of Node LTS. I lean toward@latest
just because I would like to integrateNPM Audit
, take a look at #201.@dhritzkiv, I know you have been dealing with releasing package-lock.json for most repositories, I'm going to test if my changes are compatible with older versions, if not I will revert my change.
We might also consider adding engines to package.json with our recommended version of NPM.