2016-01-06 04:06:47 +01:00
|
|
|
{
|
|
|
|
|
"name": "silverstripe-framework",
|
|
|
|
|
"version": "4.0.0",
|
|
|
|
|
"description": "The SilverStripe framework",
|
|
|
|
|
"directories": {
|
|
|
|
|
"doc": "docs",
|
|
|
|
|
"test": "tests"
|
|
|
|
|
},
|
|
|
|
|
"engines": {
|
2016-03-14 17:16:38 +01:00
|
|
|
"node": "^4.2.0"
|
2016-01-06 04:06:47 +01:00
|
|
|
},
|
|
|
|
|
"scripts": {
|
2017-02-21 03:32:25 +01:00
|
|
|
"build": "webpack --bail --progress",
|
|
|
|
|
"watch": "webpack --progress --config ./webpack-dev.config.js --watch",
|
API Use Webpack
The bundle is generated by running “webpack” directly - gulp is no
longer needed as an intermediary. The resulting config is a lot shorter,
although more configuration is pushed into lib.js.
Modules are shared between javascript files as global variables.
Although this global state pollution is a bit messy, I don’t think it’s
practically any worse than the previous state, and it highlights the
heavy coupling between the different packages we have in place.
Reducing the width of the coupling between the core javascript and
add-on modules would probably be a better way of dealing with this than
replacing global variables with some other kind of global state.
The web pack execution seems roughly twice as fast - if I clear out my
framework/client/dist/js folder, it takes 13.3s to rebuild. However,
it’s not rebuilding other files inside dist, only the bundle files.
CSS files are now included from javascript and incorporated into
bundle.css by the webpack. Although the style-loader is helpful in some
dev workflows (it allows live reload), it introduces a flash of
unstyled content which makes it inappropriate for production.
Instead ExtractTextPlugin is used to write all the aggregated CSS
into a single bundle.css file. A style-loader-based configuration could
be introduced for dev environments, if we make use of the webpack live
reloader in the future.
Note that the following features have been removed as they don't appear to be
necessary when using Webpack:
- UMD module generation
- thirdparty dist file copying
LeftAndMain.js deps: Without it, ssui.core.js gets loaded too late,
which leads e.g. to buttons being initialised without this added behaviour.
2016-08-21 03:17:50 +02:00
|
|
|
"css": "WEBPACK_CHILD=css webpack",
|
2016-03-16 01:30:39 +01:00
|
|
|
"lock": "npm-shrinkwrap --dev",
|
2016-04-19 11:04:43 +02:00
|
|
|
"test": "NODE_PATH=\"./client/src:./admin/client/src\" jest",
|
|
|
|
|
"coverage": "NODE_PATH=\"./client/src:./admin/client/src\" jest --coverage",
|
2017-01-09 11:46:28 +01:00
|
|
|
"lint": "eslint client/src && eslint admin/client/src && sass-lint -v"
|
2016-01-06 04:06:47 +01:00
|
|
|
},
|
|
|
|
|
"repository": {
|
|
|
|
|
"type": "git",
|
|
|
|
|
"url": "git://github.com/silverstripe/silverstripe-framework.git"
|
|
|
|
|
},
|
|
|
|
|
"keywords": [
|
|
|
|
|
"silverstripe",
|
|
|
|
|
"framework"
|
|
|
|
|
],
|
|
|
|
|
"author": "SilverStripe Ltd",
|
|
|
|
|
"license": "BSD-3-Clause",
|
|
|
|
|
"bugs": {
|
|
|
|
|
"url": "https://github.com/silverstripe/silverstripe-framework/issues"
|
|
|
|
|
},
|
|
|
|
|
"homepage": "https://github.com/silverstripe/silverstripe-framework#readme",
|
2016-03-22 04:27:44 +01:00
|
|
|
"dependencies": {
|
2016-09-21 07:14:43 +02:00
|
|
|
"apollo-client": "^0.5.5",
|
2016-04-12 02:15:37 +02:00
|
|
|
"babel-polyfill": "^6.7.4",
|
2016-09-07 12:21:43 +02:00
|
|
|
"blueimp-file-upload": "6.0.3",
|
|
|
|
|
"blueimp-load-image": "1.1.3",
|
|
|
|
|
"blueimp-tmpl": "1.0.2",
|
|
|
|
|
"bootstrap": "4.0.0-alpha.2",
|
API Use Webpack
The bundle is generated by running “webpack” directly - gulp is no
longer needed as an intermediary. The resulting config is a lot shorter,
although more configuration is pushed into lib.js.
Modules are shared between javascript files as global variables.
Although this global state pollution is a bit messy, I don’t think it’s
practically any worse than the previous state, and it highlights the
heavy coupling between the different packages we have in place.
Reducing the width of the coupling between the core javascript and
add-on modules would probably be a better way of dealing with this than
replacing global variables with some other kind of global state.
The web pack execution seems roughly twice as fast - if I clear out my
framework/client/dist/js folder, it takes 13.3s to rebuild. However,
it’s not rebuilding other files inside dist, only the bundle files.
CSS files are now included from javascript and incorporated into
bundle.css by the webpack. Although the style-loader is helpful in some
dev workflows (it allows live reload), it introduces a flash of
unstyled content which makes it inappropriate for production.
Instead ExtractTextPlugin is used to write all the aggregated CSS
into a single bundle.css file. A style-loader-based configuration could
be introduced for dev environments, if we make use of the webpack live
reloader in the future.
Note that the following features have been removed as they don't appear to be
necessary when using Webpack:
- UMD module generation
- thirdparty dist file copying
LeftAndMain.js deps: Without it, ssui.core.js gets loaded too late,
which leads e.g. to buttons being initialised without this added behaviour.
2016-08-21 03:17:50 +02:00
|
|
|
"chosen-js": "^1.5.1",
|
2016-07-07 00:39:44 +02:00
|
|
|
"deep-equal": "^1.0.1",
|
2016-06-16 05:04:14 +02:00
|
|
|
"deep-freeze-strict": "^1.1.1",
|
2016-03-29 04:38:48 +02:00
|
|
|
"es6-promise": "^3.1.2",
|
2016-09-21 07:14:43 +02:00
|
|
|
"graphql-fragments": "^0.1.0",
|
|
|
|
|
"graphql-tag": "^0.1.17",
|
2016-07-14 07:51:01 +02:00
|
|
|
"history": "^2.1.2",
|
2016-03-29 04:38:48 +02:00
|
|
|
"isomorphic-fetch": "https://registry.npmjs.org/isomorphic-fetch/-/isomorphic-fetch-2.2.1.tgz",
|
2016-03-22 04:27:44 +01:00
|
|
|
"jquery-sizes": "^0.33.0",
|
2016-04-07 13:43:43 +02:00
|
|
|
"json-js": "^1.1.2",
|
2016-04-17 22:25:53 +02:00
|
|
|
"merge": "^1.2.0",
|
2016-03-22 04:27:44 +01:00
|
|
|
"page.js": "^4.13.3",
|
2016-04-11 08:21:33 +02:00
|
|
|
"qs": "^6.1.0",
|
2016-09-02 03:44:21 +02:00
|
|
|
"react": "^15.3.1",
|
2016-08-28 08:40:32 +02:00
|
|
|
"react-addons-css-transition-group": "^15.3.1",
|
2016-09-21 07:14:43 +02:00
|
|
|
"react-apollo": "^0.7.0",
|
2016-11-22 03:18:26 +01:00
|
|
|
"react-bootstrap-ss": "^0.30.6",
|
2017-02-19 23:34:18 +01:00
|
|
|
"react-dnd": "^2.2.3",
|
|
|
|
|
"react-dnd-html5-backend": "^2.2.3",
|
2016-09-02 03:44:21 +02:00
|
|
|
"react-dom": "^15.3.1",
|
2016-03-30 11:03:22 +02:00
|
|
|
"react-redux": "^4.4.1",
|
2016-07-14 07:51:01 +02:00
|
|
|
"react-router": "^2.4.1",
|
|
|
|
|
"react-router-redux": "^4.0.5",
|
2016-03-29 04:38:48 +02:00
|
|
|
"redux": "https://registry.npmjs.org/redux/-/redux-3.0.5.tgz",
|
2016-10-12 03:47:14 +02:00
|
|
|
"redux-form": "^6.0.2",
|
2016-07-14 07:51:01 +02:00
|
|
|
"redux-thunk": "^2.1.0",
|
2016-07-07 00:39:44 +02:00
|
|
|
"tether": "^1.3.2",
|
2016-11-02 01:42:44 +01:00
|
|
|
"url": "^0.11.0",
|
|
|
|
|
"validator": "^6.1.0"
|
2016-03-22 04:27:44 +01:00
|
|
|
},
|
2016-01-06 04:06:47 +01:00
|
|
|
"devDependencies": {
|
API Use Webpack
The bundle is generated by running “webpack” directly - gulp is no
longer needed as an intermediary. The resulting config is a lot shorter,
although more configuration is pushed into lib.js.
Modules are shared between javascript files as global variables.
Although this global state pollution is a bit messy, I don’t think it’s
practically any worse than the previous state, and it highlights the
heavy coupling between the different packages we have in place.
Reducing the width of the coupling between the core javascript and
add-on modules would probably be a better way of dealing with this than
replacing global variables with some other kind of global state.
The web pack execution seems roughly twice as fast - if I clear out my
framework/client/dist/js folder, it takes 13.3s to rebuild. However,
it’s not rebuilding other files inside dist, only the bundle files.
CSS files are now included from javascript and incorporated into
bundle.css by the webpack. Although the style-loader is helpful in some
dev workflows (it allows live reload), it introduces a flash of
unstyled content which makes it inappropriate for production.
Instead ExtractTextPlugin is used to write all the aggregated CSS
into a single bundle.css file. A style-loader-based configuration could
be introduced for dev environments, if we make use of the webpack live
reloader in the future.
Note that the following features have been removed as they don't appear to be
necessary when using Webpack:
- UMD module generation
- thirdparty dist file copying
LeftAndMain.js deps: Without it, ssui.core.js gets loaded too late,
which leads e.g. to buttons being initialised without this added behaviour.
2016-08-21 03:17:50 +02:00
|
|
|
"autoprefixer": "^6.4.0",
|
2016-03-30 11:17:32 +02:00
|
|
|
"babel-core": "^6.7.4",
|
2016-03-16 01:30:39 +01:00
|
|
|
"babel-jest": "^9.0.3",
|
API Use Webpack
The bundle is generated by running “webpack” directly - gulp is no
longer needed as an intermediary. The resulting config is a lot shorter,
although more configuration is pushed into lib.js.
Modules are shared between javascript files as global variables.
Although this global state pollution is a bit messy, I don’t think it’s
practically any worse than the previous state, and it highlights the
heavy coupling between the different packages we have in place.
Reducing the width of the coupling between the core javascript and
add-on modules would probably be a better way of dealing with this than
replacing global variables with some other kind of global state.
The web pack execution seems roughly twice as fast - if I clear out my
framework/client/dist/js folder, it takes 13.3s to rebuild. However,
it’s not rebuilding other files inside dist, only the bundle files.
CSS files are now included from javascript and incorporated into
bundle.css by the webpack. Although the style-loader is helpful in some
dev workflows (it allows live reload), it introduces a flash of
unstyled content which makes it inappropriate for production.
Instead ExtractTextPlugin is used to write all the aggregated CSS
into a single bundle.css file. A style-loader-based configuration could
be introduced for dev environments, if we make use of the webpack live
reloader in the future.
Note that the following features have been removed as they don't appear to be
necessary when using Webpack:
- UMD module generation
- thirdparty dist file copying
LeftAndMain.js deps: Without it, ssui.core.js gets loaded too late,
which leads e.g. to buttons being initialised without this added behaviour.
2016-08-21 03:17:50 +02:00
|
|
|
"babel-loader": "^6.2.5",
|
2016-03-30 11:17:32 +02:00
|
|
|
"babel-plugin-transform-es2015-modules-umd": "^6.6.5",
|
2016-04-04 02:01:43 +02:00
|
|
|
"babel-plugin-transform-object-assign": "^6.5.0",
|
2016-07-14 07:51:01 +02:00
|
|
|
"babel-plugin-transform-object-rest-spread": "^6.8.0",
|
2016-03-16 01:30:39 +01:00
|
|
|
"babel-preset-es2015": "^6.6.0",
|
|
|
|
|
"babel-preset-react": "^6.5.0",
|
API Use Webpack
The bundle is generated by running “webpack” directly - gulp is no
longer needed as an intermediary. The resulting config is a lot shorter,
although more configuration is pushed into lib.js.
Modules are shared between javascript files as global variables.
Although this global state pollution is a bit messy, I don’t think it’s
practically any worse than the previous state, and it highlights the
heavy coupling between the different packages we have in place.
Reducing the width of the coupling between the core javascript and
add-on modules would probably be a better way of dealing with this than
replacing global variables with some other kind of global state.
The web pack execution seems roughly twice as fast - if I clear out my
framework/client/dist/js folder, it takes 13.3s to rebuild. However,
it’s not rebuilding other files inside dist, only the bundle files.
CSS files are now included from javascript and incorporated into
bundle.css by the webpack. Although the style-loader is helpful in some
dev workflows (it allows live reload), it introduces a flash of
unstyled content which makes it inappropriate for production.
Instead ExtractTextPlugin is used to write all the aggregated CSS
into a single bundle.css file. A style-loader-based configuration could
be introduced for dev environments, if we make use of the webpack live
reloader in the future.
Note that the following features have been removed as they don't appear to be
necessary when using Webpack:
- UMD module generation
- thirdparty dist file copying
LeftAndMain.js deps: Without it, ssui.core.js gets loaded too late,
which leads e.g. to buttons being initialised without this added behaviour.
2016-08-21 03:17:50 +02:00
|
|
|
"css-loader": "^0.23.1",
|
2016-03-30 23:45:54 +02:00
|
|
|
"eslint": "^2.5.3",
|
|
|
|
|
"eslint-config-airbnb": "^6.2.0",
|
|
|
|
|
"eslint-plugin-react": "^4.2.3",
|
API Use Webpack
The bundle is generated by running “webpack” directly - gulp is no
longer needed as an intermediary. The resulting config is a lot shorter,
although more configuration is pushed into lib.js.
Modules are shared between javascript files as global variables.
Although this global state pollution is a bit messy, I don’t think it’s
practically any worse than the previous state, and it highlights the
heavy coupling between the different packages we have in place.
Reducing the width of the coupling between the core javascript and
add-on modules would probably be a better way of dealing with this than
replacing global variables with some other kind of global state.
The web pack execution seems roughly twice as fast - if I clear out my
framework/client/dist/js folder, it takes 13.3s to rebuild. However,
it’s not rebuilding other files inside dist, only the bundle files.
CSS files are now included from javascript and incorporated into
bundle.css by the webpack. Although the style-loader is helpful in some
dev workflows (it allows live reload), it introduces a flash of
unstyled content which makes it inappropriate for production.
Instead ExtractTextPlugin is used to write all the aggregated CSS
into a single bundle.css file. A style-loader-based configuration could
be introduced for dev environments, if we make use of the webpack live
reloader in the future.
Note that the following features have been removed as they don't appear to be
necessary when using Webpack:
- UMD module generation
- thirdparty dist file copying
LeftAndMain.js deps: Without it, ssui.core.js gets loaded too late,
which leads e.g. to buttons being initialised without this added behaviour.
2016-08-21 03:17:50 +02:00
|
|
|
"expose-loader": "^0.7.1",
|
|
|
|
|
"extract-text-webpack-plugin": "^1.0.1",
|
|
|
|
|
"file-loader": "^0.9.0",
|
2016-09-07 12:21:43 +02:00
|
|
|
"imports-loader": "^0.6.5",
|
2016-03-16 01:30:39 +01:00
|
|
|
"jest-cli": "^0.9.2",
|
API Use Webpack
The bundle is generated by running “webpack” directly - gulp is no
longer needed as an intermediary. The resulting config is a lot shorter,
although more configuration is pushed into lib.js.
Modules are shared between javascript files as global variables.
Although this global state pollution is a bit messy, I don’t think it’s
practically any worse than the previous state, and it highlights the
heavy coupling between the different packages we have in place.
Reducing the width of the coupling between the core javascript and
add-on modules would probably be a better way of dealing with this than
replacing global variables with some other kind of global state.
The web pack execution seems roughly twice as fast - if I clear out my
framework/client/dist/js folder, it takes 13.3s to rebuild. However,
it’s not rebuilding other files inside dist, only the bundle files.
CSS files are now included from javascript and incorporated into
bundle.css by the webpack. Although the style-loader is helpful in some
dev workflows (it allows live reload), it introduces a flash of
unstyled content which makes it inappropriate for production.
Instead ExtractTextPlugin is used to write all the aggregated CSS
into a single bundle.css file. A style-loader-based configuration could
be introduced for dev environments, if we make use of the webpack live
reloader in the future.
Note that the following features have been removed as they don't appear to be
necessary when using Webpack:
- UMD module generation
- thirdparty dist file copying
LeftAndMain.js deps: Without it, ssui.core.js gets loaded too late,
which leads e.g. to buttons being initialised without this added behaviour.
2016-08-21 03:17:50 +02:00
|
|
|
"node-sass": "^3.8.0",
|
2016-08-28 08:40:32 +02:00
|
|
|
"npm-shrinkwrap": "^6.0.1",
|
API Use Webpack
The bundle is generated by running “webpack” directly - gulp is no
longer needed as an intermediary. The resulting config is a lot shorter,
although more configuration is pushed into lib.js.
Modules are shared between javascript files as global variables.
Although this global state pollution is a bit messy, I don’t think it’s
practically any worse than the previous state, and it highlights the
heavy coupling between the different packages we have in place.
Reducing the width of the coupling between the core javascript and
add-on modules would probably be a better way of dealing with this than
replacing global variables with some other kind of global state.
The web pack execution seems roughly twice as fast - if I clear out my
framework/client/dist/js folder, it takes 13.3s to rebuild. However,
it’s not rebuilding other files inside dist, only the bundle files.
CSS files are now included from javascript and incorporated into
bundle.css by the webpack. Although the style-loader is helpful in some
dev workflows (it allows live reload), it introduces a flash of
unstyled content which makes it inappropriate for production.
Instead ExtractTextPlugin is used to write all the aggregated CSS
into a single bundle.css file. A style-loader-based configuration could
be introduced for dev environments, if we make use of the webpack live
reloader in the future.
Note that the following features have been removed as they don't appear to be
necessary when using Webpack:
- UMD module generation
- thirdparty dist file copying
LeftAndMain.js deps: Without it, ssui.core.js gets loaded too late,
which leads e.g. to buttons being initialised without this added behaviour.
2016-08-21 03:17:50 +02:00
|
|
|
"postcss-loader": "^0.10.1",
|
2016-09-02 03:44:21 +02:00
|
|
|
"react-addons-test-utils": "^15.3.1",
|
2016-03-16 01:30:39 +01:00
|
|
|
"redux-logger": "^2.6.1",
|
FIX Webpack handles images & fonts.
Responsibility for finding and referencing images and fonts is now
given to webpack. All the url references are now relative to the
component scss file, and point to font & images files in src/, rather
than assuming someone else will place them in dist.
This makes the source more modular, and makes it easier to, for
example, inline images are data URIs, or create a new build script that
builds several modules for a project in a single pass.
Workaround for bad font path in bundle.css:
ExtactTextPlugin didn’t work as well with a subfolder reference in the
filename. This is just a short-term fix and could probably be improved
to put bundle.css back in the styles subfolder.
Webpack handles images & fonts:
Responsibility for finding and referencing images and fonts is now
given to webpack. All the url references are now relative to the
component scss file, and point to font & images files in src/, rather
than assuming someone else will place them in dist.
This makes the source more modular, and makes it easier to, for
example, inline images are data URIs, or create a new build script that
builds several modules for a project in a single pass.
Clarify docs on spriting and webfonts:
We've decided to remove sprity since it comes with hundreds of dependencies,
and needs compilation within the "npm install" - dragging out the already overweight
install process, and making the resulting node_modules/ folder less portable between systems.
2016-08-26 05:37:43 +02:00
|
|
|
"resolve-url-loader": "^1.6.0",
|
2016-09-17 05:30:30 +02:00
|
|
|
"sass-lint": "^1.9.1",
|
API Use Webpack
The bundle is generated by running “webpack” directly - gulp is no
longer needed as an intermediary. The resulting config is a lot shorter,
although more configuration is pushed into lib.js.
Modules are shared between javascript files as global variables.
Although this global state pollution is a bit messy, I don’t think it’s
practically any worse than the previous state, and it highlights the
heavy coupling between the different packages we have in place.
Reducing the width of the coupling between the core javascript and
add-on modules would probably be a better way of dealing with this than
replacing global variables with some other kind of global state.
The web pack execution seems roughly twice as fast - if I clear out my
framework/client/dist/js folder, it takes 13.3s to rebuild. However,
it’s not rebuilding other files inside dist, only the bundle files.
CSS files are now included from javascript and incorporated into
bundle.css by the webpack. Although the style-loader is helpful in some
dev workflows (it allows live reload), it introduces a flash of
unstyled content which makes it inappropriate for production.
Instead ExtractTextPlugin is used to write all the aggregated CSS
into a single bundle.css file. A style-loader-based configuration could
be introduced for dev environments, if we make use of the webpack live
reloader in the future.
Note that the following features have been removed as they don't appear to be
necessary when using Webpack:
- UMD module generation
- thirdparty dist file copying
LeftAndMain.js deps: Without it, ssui.core.js gets loaded too late,
which leads e.g. to buttons being initialised without this added behaviour.
2016-08-21 03:17:50 +02:00
|
|
|
"sass-loader": "^4.0.0",
|
|
|
|
|
"script-loader": "^0.7.0",
|
2016-01-11 02:25:30 +01:00
|
|
|
"semver": "^5.1.0",
|
FIX Webpack handles images & fonts.
Responsibility for finding and referencing images and fonts is now
given to webpack. All the url references are now relative to the
component scss file, and point to font & images files in src/, rather
than assuming someone else will place them in dist.
This makes the source more modular, and makes it easier to, for
example, inline images are data URIs, or create a new build script that
builds several modules for a project in a single pass.
Workaround for bad font path in bundle.css:
ExtactTextPlugin didn’t work as well with a subfolder reference in the
filename. This is just a short-term fix and could probably be improved
to put bundle.css back in the styles subfolder.
Webpack handles images & fonts:
Responsibility for finding and referencing images and fonts is now
given to webpack. All the url references are now relative to the
component scss file, and point to font & images files in src/, rather
than assuming someone else will place them in dist.
This makes the source more modular, and makes it easier to, for
example, inline images are data URIs, or create a new build script that
builds several modules for a project in a single pass.
Clarify docs on spriting and webfonts:
We've decided to remove sprity since it comes with hundreds of dependencies,
and needs compilation within the "npm install" - dragging out the already overweight
install process, and making the resulting node_modules/ folder less portable between systems.
2016-08-26 05:37:43 +02:00
|
|
|
"url-loader": "^0.5.7",
|
API Use Webpack
The bundle is generated by running “webpack” directly - gulp is no
longer needed as an intermediary. The resulting config is a lot shorter,
although more configuration is pushed into lib.js.
Modules are shared between javascript files as global variables.
Although this global state pollution is a bit messy, I don’t think it’s
practically any worse than the previous state, and it highlights the
heavy coupling between the different packages we have in place.
Reducing the width of the coupling between the core javascript and
add-on modules would probably be a better way of dealing with this than
replacing global variables with some other kind of global state.
The web pack execution seems roughly twice as fast - if I clear out my
framework/client/dist/js folder, it takes 13.3s to rebuild. However,
it’s not rebuilding other files inside dist, only the bundle files.
CSS files are now included from javascript and incorporated into
bundle.css by the webpack. Although the style-loader is helpful in some
dev workflows (it allows live reload), it introduces a flash of
unstyled content which makes it inappropriate for production.
Instead ExtractTextPlugin is used to write all the aggregated CSS
into a single bundle.css file. A style-loader-based configuration could
be introduced for dev environments, if we make use of the webpack live
reloader in the future.
Note that the following features have been removed as they don't appear to be
necessary when using Webpack:
- UMD module generation
- thirdparty dist file copying
LeftAndMain.js deps: Without it, ssui.core.js gets loaded too late,
which leads e.g. to buttons being initialised without this added behaviour.
2016-08-21 03:17:50 +02:00
|
|
|
"webpack": "^1.13.2"
|
2016-01-06 04:06:47 +01:00
|
|
|
},
|
2016-03-16 01:30:39 +01:00
|
|
|
"jest": {
|
|
|
|
|
"scriptPreprocessor": "<rootDir>/node_modules/babel-jest",
|
|
|
|
|
"testPathDirs": [
|
2016-04-19 01:55:45 +02:00
|
|
|
"admin/client/src",
|
|
|
|
|
"client/src"
|
2016-03-16 01:30:39 +01:00
|
|
|
],
|
|
|
|
|
"testDirectoryName": "tests",
|
|
|
|
|
"mocksPattern": "mocks",
|
|
|
|
|
"unmockedModulePathPatterns": [
|
2016-09-29 02:42:53 +02:00
|
|
|
"<rootDir>/node_modules/react",
|
2016-10-12 03:47:14 +02:00
|
|
|
"<rootDir>/node_modules/qs",
|
|
|
|
|
"<rootDir>/node_modules/redux-form"
|
2016-03-16 01:30:39 +01:00
|
|
|
],
|
|
|
|
|
"bail": true,
|
|
|
|
|
"testRunner": "<rootDir>/node_modules/jest-cli/src/testRunners/jasmine/jasmine2.js"
|
|
|
|
|
},
|
|
|
|
|
"babel": {
|
|
|
|
|
"presets": [
|
2016-03-18 02:42:45 +01:00
|
|
|
"react",
|
2016-03-16 01:30:39 +01:00
|
|
|
"es2015"
|
|
|
|
|
]
|
2016-01-06 04:06:47 +01:00
|
|
|
}
|
|
|
|
|
}
|
