Grunt 1.0.0 rc1 releasedPosted on February 11, 2016
The Grunt team is pleased to announce the first release candidate for
This release focuses on fixing critical issues and improved support with Node.js
v0.10, v0.12, v4.0, v5.0 and io.js on Windows, OSX and Linux. We ask you to test the
rc1 and report any issues you are experiencing.
npm install firstname.lastname@example.org --save-dev
Be advised Grunt
1.0.0 will no longer support Node.js v0.8.
If you have a Grunt plugin that includes
grunt in the
peerDependencies section of your
package.json, we recommend tagging with
"grunt": ">=0.4.0". Otherwise when
email@example.com is released, npm@2 users will receive a hard error when trying to install your plugin and npm@3 users will get a warning.
Be aware, peer dependencies are no longer installed for users as of npm@3. Users of Grunt plugins are expected to
npm install grunt --save-dev alongside any Grunt plugin install.
We ask you to send pull requests to your favourite plugins and ask them to update the
peerDependencies section of their
We have created an new repo to encourage members of the community interested in shaping the future of Grunt to submit a RFC.
Submitting an RFC will allow you to formally propose a significant change to Grunt and elicit feedback from the core team and community.
The active proposals will help portray the future roadmap for Grunt and hopefully expedite community contributions into future Grunt releases.
We now install
grunt-cli as part of
grunt. Many users do not wish to perform
the extra step of
npm install grunt-cli -g. To better conform to the idioms
of Node.js, you can now
npm install grunt --save-dev then include Grunt in your
Your users now only have to
npm install and
npm run grunt to run your
npm >= 2.0.0 can also pass tasks and options with:
npm run grunt -- task --option=foo which is equivalent to
grunt task --option=foo.
If you would like the
grunt command on your computer, please continue to
npm install grunt-cli -g and use as before.
Be aware, some APIs have changed warranting a major version update:
coffee-scriptis upgraded to
~1.10.0which could incur breaking changes when using the language with plugins and Gruntfiles.
noptis upgraded to
~3.0.6which has fixed many issues, including passing multiple arguments and dealing with numbers as options. Be aware previously
--foo barused to pass the value
'bar'to the option
foo. It will now set the option
trueand run the task
globis upgraded to
minimatchis upgraded to
~3.0.0. Results are now sorted by default with
grunt.file.expandMapping(). Pass the
nosort: trueoption if you don't want the results to be sorted.
lodashwas upgraded to
~4.3.0. Many changes have occurred. Some of which that directly affect Grunt are
grunt.util._.template()returns a compile function and
grunt.util._.flattenno longer flattens deeply.
grunt.util._is deprecated and we highly encourage you to
npm install lodashand
var _ = require('lodash')to use
lodash. Please see the lodash changelog for a full list of changes: https://github.com/lodash/lodash/wiki/Changelog
iconv-liteis upgraded to
~0.4.13and strips the BOM by default.
js-yamlis upgraded to
~3.5.2and may affect
grunt.file.readYAML. We encourage you to please
npm install js-yamland use
var YAML = require('js-yaml')directly in case of future deprecations.
- A file
modeoption can be passed into grunt.file.write().
Done, without errors.was changed to
Done.to avoid failing by mistake on the word
We encourage you to try out this release.
We are also looking for contributors to all Grunt repositories and are willing to mentor you to get more experience with open source.
comments powered byDisqus