Files
meteor/scripts/dev-bundle-server-package.js
Ben Newman da11c28ed4 Use the official fibers@4.0.3 release.
This includes https://github.com/laverdet/node-fibers/pull/429, fixing the
CPU spikes reported and discussed here: https://github.com/meteor/meteor/pull/10527#issuecomment-567982128

Using an official fibers release rather than a GitHub URL is preferable
because it doesn't require building fibers from source when deploying a
Meteor app to production, and also doesn't rely on GitHub being
operational, though of course it does rely on other networked services
like npm.
2020-01-07 20:31:28 -05:00

34 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: {
// Keep the versions of these packages consistent with the versions
// found in dev-bundle-tool-package.js.
fibers: "4.0.3",
"meteor-promise": "0.8.7",
promise: "8.0.2",
reify: "0.20.12",
"@babel/parser": "7.7.5",
"@types/underscore": "1.9.2",
underscore: "1.9.1",
"source-map-support": "https://github.com/meteor/node-source-map-support/tarball/1912478769d76e5df4c365e147f25896aee6375e",
"@types/semver": "5.4.0",
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');