Reputation: 5911
Every day when I run meteor for the first time, meteor goes out to the internet to check for updates in the npm packages.
If I don't have internet connection, I can't run meteor. This kills my productivity. I would like to force this update to not run so I can work.
My command line is:
NODE_OPTIONS=--debug meteor
The output is:
=> Started proxy.
=> Started MongoDB.
npm: updating npm dependencies -- github, colors, aws-sdk, moment, string, urlify, sendgrid, airbrake...
iron-router: updating npm dependencies -- connect...
meteor-collection-management: updating npm dependencies -- mongodb...
kadira: updating npm dependencies -- debug, usage...
Now here is the additional puzzlement. My package.json explicitly specifies the versions of the npm packages.
more packages.json
{
"github": "0.1.15",
"colors": "0.6.2",
"aws-sdk": "2.0.0-rc13",
"moment": "2.5.1",
"string": "1.8.0",
"urlify": "0.3.5",
"sendgrid": "1.0.2",
"airbrake": "0.3.8"
}
The list and versions haven't changed in ages. npm should have no reason to go to the web - it has local copies of the specified versions already.
Now of course there is a possibility that this update is triggered by a sub-dependency - which is why I would like to do:
UPDATE: I am sort of working around this problem with https://www.npmjs.org/package/sinopia
These related? issues are also showing up on startup:
Package.on_test runs even when not testing
Why does Meteor-Npm keep trying to get a package from the internet
Upvotes: 1
Views: 802