Specify a few more version constraints in coffeescript packages.

Small follow-up to #9018.

Note (especially @GeoffreyBooth): these version constraints do two things:
(1) specify a minimum version, and (2) fix the major version. In other
words, the coffeescript package should not need to be republished when we
publish new minor versions of these core packages in Meteor 1.5.2 or 1.6.

When/if we publish a new major version of these packages, the coffeescript
package can simply bump its version constraints, but that probably won't
happen any time soon. I think that's reasonable because a major version
bump suggests there are some significant changes that need to be
acknowledged by dependent packages.
This commit is contained in:
Ben Newman
2017-08-17 09:44:07 -04:00
parent 568e695eeb
commit 65c8b481e2
2 changed files with 5 additions and 5 deletions

View File

@@ -1,10 +1,10 @@
Package.describe({
summary: "Used by the coffeescript package's tests",
version: "1.0.8"
version: "1.0.9"
});
Package.onUse(function (api) {
api.use('coffeescript', ['client', 'server']);
api.use('coffeescript@1.12.7', ['client', 'server']);
api.export('COFFEESCRIPT_EXPORTED');
api.export('COFFEESCRIPT_EXPORTED_ONE_MORE');
api.export('COFFEESCRIPT_EXPORTED_WITH_BACKTICKS');

View File

@@ -24,9 +24,9 @@ Package.onUse(function (api) {
// same runtime environment that the 'ecmascript' package provides.
// The following api.imply calls should match those in ../../ecmascript/package.js,
// except that coffeescript does not api.imply('modules').
api.imply('ecmascript-runtime', 'server');
api.imply('babel-runtime');
api.imply('promise');
api.imply('ecmascript-runtime@0.4.1', 'server');
api.imply('babel-runtime@1.0.1');
api.imply('promise@0.8.9');
});
Package.onTest(function (api) {