Package.describe({
  name: 'standard-minifier-css',
  version: '1.3.3',
  summary: 'Standard css minifier used with Meteor apps by default.',
  documentation: 'README.md'
});

Package.registerBuildPlugin({
  name: "minifyStdCSS",
  use: [
    'minifier-css@1.2.14'
  ],
  npmDependencies: {
    "source-map": "0.5.6",
    "lru-cache": "4.0.1"
  },
  sources: [
    'plugin/minify-css.js'
  ]
});

Package.onUse(function(api) {
  api.use('isobuild:minifier-plugin@1.0.0');
});

Package.describe({
  name: 'standard-minifier-css',
  version: '1.3.3',
  summary: 'Standard css minifier used with Meteor apps by default.',
  documentation: 'README.md'
});

Package.registerBuildPlugin({
  name: "minifyStdCSS",
  use: [
    'minifier-css'
  ],
  npmDependencies: {
    "source-map": "0.5.6",
    "lru-cache": "4.0.1"
  },
  sources: [
    'plugin/minify-css.js'
  ]
});

Package.onUse(function(api) {
  api.use('isobuild:minifier-plugin@1.0.0');
});

Remove version constraint from minifier-css in standard-minifier-css.
Remove version constraint from minifier-css in standard-minifier-css.

This restriction was preventing the standard-minifier-css from getting
the latest updates to minifier-css.  Typically, when publishing
a package outside of a release cycle, I believe we need to manually add
this constraint since `meteor publish-release` normally takes care of it
automatically, however in most cases, I don't believe this should be
(permanently) committed.

I may stand to be corrected, but will find out soon!
