tonyair
/
silverstripe-cms
mirror of https://github.com/silverstripe/silverstripe-cms
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
silverstripe-cms/.gitignore

6 lines
66 B
Plaintext
Raw Permalink Normal View History

JS build tooling fixes - Relaxed NodeJS dependency to 4.x - Switch to NPM "dependencies" (rather than dev) Provides consistency with framework, where these had previously been broken out between "dependencies" and "devDependencies", which in turn caused issues with "npm shrinkwrap" - Add npm-shrinkwrap.json: Consistent with framework approach Using uber's wrapper library since it prevents npm shrinkwrap from failing on file generation, as well as actually suceeding with an "npm install" once the file is present. - Don't add comments to dist files via babelify We've had some issues with different dependencies causing different results based on the environment, which in turn causes unnecessary diffs - making our work harder to review. Comments can be read through the ES6 source files, and through source maps when generated through `npm run build --development` - Make JS build tooling and naming consistent with framework
2016-02-11 20:33:04 +01:00
node_modules
NEW: Simplified travis run Travis no longer relies on travis-support or special project structures. Instead, behat and silverstripe-serve are provided as dev dependencies and used within a normal composer install structure. tests/fixtures/Page.php should be copied into the project root before a test run. .travis.yml does this.
2016-10-25 00:56:30 +02:00
silverstripe-cache
vendor
JS build tooling fixes - Relaxed NodeJS dependency to 4.x - Switch to NPM "dependencies" (rather than dev) Provides consistency with framework, where these had previously been broken out between "dependencies" and "devDependencies", which in turn caused issues with "npm shrinkwrap" - Add npm-shrinkwrap.json: Consistent with framework approach Using uber's wrapper library since it prevents npm shrinkwrap from failing on file generation, as well as actually suceeding with an "npm install" once the file is present. - Don't add comments to dist files via babelify We've had some issues with different dependencies causing different results based on the environment, which in turn causes unnecessary diffs - making our work harder to review. Comments can be read through the ES6 source files, and through source maps when generated through `npm run build --development` - Make JS build tooling and naming consistent with framework
2016-02-11 20:33:04 +01:00
/**/*.js.map
FIX Switch gulp JavaScript generation to Webpack See https://github.com/silverstripe/silverstripe-framework/pull/5918
2016-08-21 03:18:54 +02:00
/**/*.css.map