Files
meteor/packages/jquery/package.js
David Glasser 43b4b30205 Release PLUGINS-PREVIEW@1
This included removing some internal version constraints. It would be
nice if package A could say "use B@2.0.0" (when both have changed), but
when they're both in the release, we need to make a release that has a
B@2.0.0-rc in it, which doesn't match that constraint. Fortunately,
constraints aren't necessary within a release anyway.
2015-07-22 23:19:11 -07:00

17 lines
670 B
JavaScript

Package.describe({
summary: "Manipulate the DOM using CSS selectors",
// XXX WHOOPS! We accidentally published jquery 1.11.2 as 1.11.3, because we
// naively thought that "call the version '1.11.2', add a comment saying that
// the next version should be '1.11.2_1'" would be sufficient to not be
// missed during the semi-automated version number bumping step. Next time, use `_0` from the start so it's obvious that something weird is happening!
version: '1.11.3-plugins.0_3' // XXX see above!!!!
});
Package.onUse(function (api) {
api.addFiles(['jquery.js', 'post.js'], 'client');
api.export('$', 'client');
api.export('jQuery', 'client');
});