Files
meteor/scripts/dev-bundle-tool-package.js
Ben Newman e83a1cfb8e Revert "Upgrade the npm npm package to version 4.1.2."
This reverts commit be0c8c3ee0.

Although we thought the upgrade from npm 3.10.9 to 4.1.2 was worthwhile
and safe, this breaking change proved problematic:
https://github.com/npm/npm/blob/latest/CHANGELOG.md#no-more-partial-shrinkwraps-breaking

Specifically, if a Meteor package uses `Npm.depends`, and does not yet
have an `.npm/package/npm-shrinkwrap.json` file, Meteor will create a
partial shrinkwrap file in order to install npm dependencies, but (with
the changes in npm@4) transitive dependencies of the package will no
longer be installed.

Upgrading npm to a new major version was probably too much of a change for
a 1.4.2.x release, anyway, so we're reverting it for 1.4.2.7.

In case you can't wait for 1.4.2.7, you can "fix" this problem for
previous versions of Meteor by running

  meteor npm install --global npm@3.10.9

You can test that this downgrade worked by running

  meteor npm version
2017-02-13 12:54:06 -05:00

69 lines
2.5 KiB
JavaScript

// This file contains a package.json for the dependencies of the command-line
// tool.
// We put this in a JS file so that it can contain comments. It is processed
// into a package.json file by generate-dev-bundle.sh.
var packageJson = {
name: "meteor-dev-bundle-tool",
// Version is not important but is needed to prevent warnings.
version: "0.0.0",
dependencies: {
// Explicit dependency because we are replacing it with a bundled version
// and we want to make sure there are no dependencies on a higher version
npm: "3.10.9",
"node-gyp": "3.4.0",
"node-pre-gyp": "0.6.30",
"meteor-babel": "0.13.0",
"meteor-promise": "0.8.0",
fibers: "1.0.15",
promise: "7.1.1",
// So that Babel 6 can emit require("babel-runtime/helpers/...") calls.
"babel-runtime": "6.9.2",
// For various ES2015 polyfills, such as Map and Set.
"meteor-ecmascript-runtime": "0.2.9",
// Not yet upgrading Underscore from 1.5.2 to 1.7.0 (which should be done
// in the package too) because we should consider using lodash instead
// (and there are backwards-incompatible changes either way).
underscore: "1.5.2",
"source-map-support": "https://github.com/meteor/node-source-map-support/tarball/1912478769d76e5df4c365e147f25896aee6375e",
semver: "4.1.0",
request: "2.47.0",
fstream: "https://github.com/meteor/fstream/tarball/cf4ea6c175355cec7bee38311e170d08c4078a5d",
tar: "2.2.1",
kexec: "2.0.2",
"source-map": "0.5.3",
"node-inspector": "0.12.8",
"v8-profiler": "5.6.5",
chalk: "0.5.1",
sqlite3: "3.1.3",
netroute: "1.0.2",
"http-proxy": "1.11.1",
"wordwrap": "0.0.2",
"moment": "2.8.4",
"rimraf": "2.4.3",
"glob": "7.0.6",
// XXX: When we update this, see if it fixes this Github issue:
// https://github.com/jgm/CommonMark/issues/276 . If it does, remove the
// workaround from the tool.
"commonmark": "0.15.0",
escope: "3.2.0",
// 2.4.0 (more or less, the package.json change isn't committed) plus our PR
// https://github.com/williamwicks/node-eachline/pull/4
eachline: "https://github.com/meteor/node-eachline/tarball/ff89722ff94e6b6a08652bf5f44c8fffea8a21da",
pathwatcher: "6.7.1",
optimism: "0.3.3",
'lru-cache': '4.0.1',
'cordova-lib': "6.3.1",
longjohn: '0.2.11'
}
};
if (process.platform === 'win32') {
// Remove dependencies that do not work on Windows
delete packageJson.dependencies.netroute;
delete packageJson.dependencies.kexec;
}
process.stdout.write(JSON.stringify(packageJson, null, 2) + '\n');