Can we have meteor just as an NPM package?

Wouldn’t it be more useful for meteor to be broken down into a series of NPM packages, having arguments that can be applied? Eg:

  "name": "some package",
  "scripts": {
    "preinstall": "node_modules/meteor/setup",
    "start": "node_modules/meteor/run",
    "build": "node_modules/meteor/bundle --output build/",
    "test": "node_modules/meteor/test"
  "devDependencies": {
    "meteor": "^1.3.0"

Can this be done? At times, I feel like this is the more straightforward and easy approach that is more compatible with node


We’re not there yet, but I believe this is likely where we’ll end up once we’ve completed the move to NPM. This is in fact our main focus after releasing 1.3. What is preventing this approach today is a rather tight coupling with our own build tool and package format, so both of these will need to be overhauled to make this possible.


Ah I see. I noticed that meteor DOES have an NPM package, I just have no clue what it actually does

That is not an official package, and I’m not sure what it is used for. It seems the last release was 3 years ago.

1 Like