Skip to content

Tags: vitrum/meteor

Tags

release/linker-pre7

Toggle release/linker-pre7's commit message
Allow "meteor --release X run-command Y --Z"

release/0.6.4.1

Toggle release/0.6.4.1's commit message
Use a commit of node-mongo-native with a unique package.json version.

Avoids confusing the npm cache.

release/0.6.4.1-rc3

Toggle release/0.6.4.1-rc3's commit message
Use a commit of node-mongo-native with a unique package.json version.

Avoids confusing the npm cache.

release/0.6.4.1-rc2

Toggle release/0.6.4.1-rc2's commit message
Add History entry for 0.6.4.1.

release/0.6.4.1-rc1

Toggle release/0.6.4.1-rc1's commit message
Use mongodb with extra null checks.

release/linker-pre6

Toggle release/linker-pre6's commit message
Store runner.js in test-in-console as an asset; extract via env var.

Allow packages to specify that files are assets, overriding any handler defined
for them. (May be useful for web workers!)

Let Assets.getBinary work before global-imports.js is executed.

release/linker-pre5

Toggle release/linker-pre5's commit message
Fix Meteor.release.

release/linker-pre4

Toggle release/linker-pre4's commit message
"meteor rebuild-all" should not try to rebuild warehouse packages.

That's because warehouse packages are now pre-built and have no source tree.

(The existing code didn't work anyway. It iterated over self.releaseManifest
instead of self.releaseManifest.packages, and the "name" and "version" arguments
to the each were reversed. So it was trying to delete directories named ".build"
inside "/Users/glasser/.meteor/packages/de0d7206ad/tools" and
"/Users/glasser/.meteor/packages/packages". Since those directories never
existed, it didn't manage to try to rebuild any packages anyway.)

release/linker-pre3

Toggle release/linker-pre3's commit message
Print error body if we get one from meteor mongo.

This got lost when we refactored to have the same interface as deploy-galaxy.

release/linker-pre2

Toggle release/linker-pre2's commit message
fix typo