Outdated packages can pose a threat to security and can have negative effects on performance. The more project dependencies you have, the harder it is to keep up with these updates. it should have its own lodash folder with lodash 2.4.1 in it.The Node Package Manager (npm) provides various features to help you install and maintain your project's dependencies.ĭependencies can become outdated over time due to bug fixes, new features, and other updates. In that same folder if you go into the grunt-angular-translate folder and look at its own node_modules. What should really happen is in your node_modules folder you will get your updated lodash (and you can check by looking at its package.json and the version inside). You can upgrade your direct dependency of lodash to its latest version but that would not update grunt-angular-translate dependency to lodash to that version and it really should not. In your case grunt-angular-translate has its own dependency on 'lodash': '~2.4.1' and you can not change it and should not try to since that package is supposed to work with that version and not with 2 versions higher package where there may be a bunch of breaking changes. Package-lock.json is a big 'map' of each of the packages your app uses and their dependencies which you can not impact.

In other words on which you have a specific dependency so your package can function. In package.json you specify which npm packages you are utilizing in your app. Metadata resolutions for previously-installed packages. To facilitate greater visibility of tree changes through readableĪnd optimize the installation process by allowing npm to skip repeated Node_modules without having to commit the directory itself.

Provide a facility for users to “time-travel” to previous states of

Teammates, deployments, and continuous integration are guaranteed to This file is intended to be committed into source repositories, andĭescribe a single representation of a dependency tree such that Installs are able to generate identical trees, regardless of Itĭescribes the exact tree that was generated, such that subsequent Npm modifies either the node_modules tree, or package.json. Package-lock.json is automatically generated for any operations where

Npm update specific package