Files
meteor/scripts/dev-bundle-server-package.js
Christian Klaussner 9cc978eb90 Make "meteor-dev-bundle" and "meteor-dev-bundle-tool" packages private (#9542)
Since these packages aren't published to the npm registry, they can be made private to avoid unnecessary warnings about missing description, repository, and license fields when installing server dependencies and generating dev bundles.
2018-01-16 15:23:10 -05:00

31 lines
1.1 KiB
JavaScript

// This file contains a package.json for the dependencies of the *BUNDLED
// SERVER* (not 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",
private: true,
dependencies: {
"meteor-promise": "0.8.6",
fibers: "2.0.0",
promise: "8.0.1",
// 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: "5.4.1"
},
// These are only used in dev mode (by shell.js) so end-users can avoid
// needing to install them if they use `npm install --production`.
devDependencies: {
split2: "2.1.1",
multipipe: "1.0.2",
chalk: "0.5.1"
}
};
process.stdout.write(JSON.stringify(packageJson, null, 2) + '\n');