Clarified impact of NPM/Browserify in changelog

This commit is contained in:
Ingo Schommer 2016-01-22 13:57:53 +13:00 committed by Damian Mooyman
parent 6cebffd89b
commit a5754674b7

View File

@ -39,14 +39,15 @@
of linked assets and file protection. of linked assets and file protection.
* `ProtectedFileController` class is used to serve up protected assets. * `ProtectedFileController` class is used to serve up protected assets.
### Front-end build tooling ### Front-end build tooling for CMS interface
* Dependency management via [npm](https://www.npmjs.com/) * Management of CMS JavaScript dependencies via [npm](https://www.npmjs.com/)
* ES6 is now available in all core JavaScript files via [Babel](https://babeljs.io/) * ES6 is now available in all core JavaScript files via [Babel](https://babeljs.io/)
* Front-end JavaScript bundling via [Browserify](http://browserify.org/) * Bundling of core JavaScript via [Browserify](http://browserify.org/)
* Build tasks managed by [Gulp](http://gulpjs.com/) * CMS build tasks managed by [Gulp](http://gulpjs.com/)
For more details see the docs on [working with client-side dependencies](../contributing/code#working-with-client-side-dependencies) For more details see the docs on [working with client-side dependencies](../contributing/code#working-with-client-side-dependencies). Note that you don't need any of these tools for running SilverStripe
or developing your own website. These improvements are mainly geared at CMS core development.
## Deprecated classes/methods ## Deprecated classes/methods