/ meteor Public
Install npm dependencies automatically when creating apps. #8108
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge.
Although I have said I do not think Meteor should run
npm installautomatically to update application
node_modules, my real concern is that Meteor should not interfere with your preferred
node_modules-related workflow, be it
yarn.lock, checking your
node_modulesinto git/mercurial/cvs, or whatever other scheme you currently have (or might adopt in the future).
node_modulesfrom the default
package.jsonfile when a new app is created will eliminate real confusion, and should not interfere with any workflows, because there is no opportunity to establish another workflow before Meteor runs
npm installthe very first time.
May make #8095 unnecessary?