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

57 lines
1.5 KiB
JSON
Raw Normal View History

Implement RFC-7 JavaScript module loader in CMS
2016-01-26 05:28:36 +01:00
{
"name": "silverstripe-cms",
"version": "4.0.0",
"description": "The SilverStripe CMS",
"directories": {
"test": "tests"
},
"engines": {
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": "4.x"
Implement RFC-7 JavaScript module loader in CMS
2016-01-26 05:28:36 +01:00
},
"scripts": {
"npm run lock" command Uses https://github.com/uber/npm-shrinkwrap instead of the built-in "npm shrinkwrap" since it works more reliably. Specifically, "npm install" doesn't fail depending on node_modules/ being installed in the local cache or not. It also makes npm-shrinkwrap.json easier to diff by more consistently ordering its output between runs. If you need any convincing that this is a problem, look at the over 400 issues related to "shrinkwrap" in https://github.com/npm/npm/search?q=shrinkwrap&type=Issues&utf8=%E2%9C%93
2016-02-29 08:51:30 +01:00
"build": "gulp build",
Added "npm run lock" command
2016-04-08 04:56:01 +02:00
"css": "gulp css",
"lock": "npm-shrinkwrap --dev"
Implement RFC-7 JavaScript module loader in CMS
2016-01-26 05:28:36 +01:00
},
"repository": {
"type": "git",
"url": "git://github.com/silverstripe/silverstripe-cms.git"
},
"keywords": [
"silverstripe",
"cms"
],
"author": "SilverStripe Ltd",
"license": "BSD-3-Clause",
"bugs": {
"url": "https://github.com/silverstripe/silverstripe-cms/issues"
},
"homepage": "https://github.com/silverstripe/silverstripe-cms#readme",
"devDependencies": {
Updated babel dependency
2016-03-30 11:17:13 +02:00
"babel-core": "^6.7.4",
"babel-plugin-transform-es2015-modules-umd": "^6.6.5",
Fix IE support by using babelify transforms
2016-04-04 21:57:49 +02:00
"babel-plugin-transform-object-assign": "^6.5.0",
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
"babel-preset-es2015": "^6.6.0",
Fix IE support by using babelify transforms
2016-04-04 21:57:49 +02:00
"babel-preset-es2015-ie": "^6.6.1",
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
"babel-preset-react": "^6.5.0",
Implement RFC-7 JavaScript module loader in CMS
2016-01-26 05:28:36 +01:00
"babelify": "^7.2.0",
"browserify": "^13.0.0",
"event-stream": "^3.3.2",
"glob": "^6.0.4",
"gulp": "^3.9.0",
"gulp-babel": "^6.1.1",
"gulp-diff": "^1.0.0",
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
"gulp-if": "^2.0.0",
Implement RFC-7 JavaScript module loader in CMS
2016-01-26 05:28:36 +01:00
"gulp-notify": "^2.2.0",
Handle CSS compilation with gulp-sass
2016-02-14 23:42:37 +01:00
"gulp-sass": "^2.2.0",
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
"gulp-sourcemaps": "^1.6.0",
Implement RFC-7 JavaScript module loader in CMS
2016-01-26 05:28:36 +01:00
"gulp-uglify": "^1.5.1",
"gulp-util": "^3.0.7",
Added "npm run lock" command
2016-04-08 04:56:01 +02:00
"npm-shrinkwrap": "https://registry.npmjs.org/npm-shrinkwrap/-/npm-shrinkwrap-5.4.1.tgz",
Implement RFC-7 JavaScript module loader in CMS
2016-01-26 05:28:36 +01:00
"semver": "^5.1.0",
"vinyl-buffer": "^1.0.0",
"vinyl-source-stream": "^1.1.0",
"watchify": "^3.7.0"
}
}