Files
meteor/packages/meteor-developer/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

21 lines
690 B
JavaScript

Package.describe({
summary: "Meteor developer accounts OAuth flow",
version: "1.1.4-plugins.0"
});
Package.onUse(function (api) {
api.use('oauth2', ['client', 'server']);
api.use('oauth', ['client', 'server']);
api.use('http', ['server']);
api.use(['underscore', 'service-configuration'], ['client', 'server']);
api.use(['random', 'templating'], 'client');
api.export('MeteorDeveloperAccounts');
api.addFiles('meteor_developer_common.js');
api.addFiles(['meteor_developer_configure.html',
'meteor_developer_configure.js'], 'client');
api.addFiles('meteor_developer_server.js', 'server');
api.addFiles('meteor_developer_client.js', 'client');
});