maxjhandsome
/
react
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
react/package.json

115 lines
3.7 KiB
JSON
Raw Normal View History

Initial public release
2013-05-30 03:46:11 +08:00
{
Move react-tools from root. ReactTools is deprecated, it doesn't belong at the root of the project. We'll remove it after 0.14 but for now this moves it so that it's contained and not intermixed with the rest of the project. The currect behavior of copying src/ into the package is maintained.
2015-06-03 05:13:11 +08:00
"name": "react-build",
"private": true,
Bump version for v16 development
2016-04-08 02:27:28 +08:00
"version": "16.0.0-alpha",
Initial public release
2013-05-30 03:46:11 +08:00
"devDependencies": {
Bundle DOM renderers into their individual UMD bundles (#7164) * Cut out isomorphic dependencies from the renderers These files reaches into isomorphic files. The ReactElement functions are exposed on the React object anyway so I can just use those instead. I also found some files that are not shared that should be in renderers shared. * Found a few more shared dependencies renderSubtreeIntoContainer is only used by the DOM renderer. It's not an addon. ReactClass isn't needed as a dependency since injection doesn't happen anymore. * Use a shim file to load addons' dependencies on DOM By replacing this intermediate file we can do the lazy loading without needing any lazy requires. This set up works with ES modules. We could also replace the globalShim thing with aliased files instead for consistency. * Bundle DOM renderers into their individual UMD bundles Instead of exposing the entire DOM renderer on the react.js package, I only expose CurrentOwner and ComponentTreeDevtool which are currently the only two modules that share __state__ with the renderers. Then I package each renderer in its own package. That could allow us to drop more server dependencies from the client package. It will also allow us to ship fiber as a separate renderer. Unminified DEV after before react.js 123kb 696kb react-with-addons.js 227kb 774kb react-dom.js 668kb 1kb react-dom-server.js 638kb 1kb Minified PROD after before react.min.js 24kb 154kb react-with-addons.min.js 37kb 166kb react-dom.min.js 149kb 1kb react-dom-server.min.js 144kb 1kb The total size for react.min.js + react-dom.min.js is +19kb larger because of the overlap between them right now. I'd like to see what an optimizing compiler can do to this. Some of that is fbjs stuff. There shouldn't need to be that much overlap so that's something we can hunt. We should keep isomorphic absolutely minimal so there's no reason for other React clones not to use it. There will be less overlap with Fiber. However, another strategy that we could do is package the isomorphic package into each renderer bundle and conditionally initialize it if it hasn't already been initialized. That way you only pay an overlap tax when there are two renderers on the page but not without it. It's also easier to just pull in one package. The downside is the versioning stuff that the separate npm package would solve. That applies to CDNs as well. ReactWithAddons is a bit weird because it is packaged into the isomorphic package but has a bunch of DOM dependencies. So we have to load them lazily since the DOM package gets initialized after.
2016-08-10 03:39:03 +08:00
"aliasify": "^2.0.0",
Add (failing) React ART tests This helps us make sure we don't break React ART in a minor or patch release. The idea is to not change these files when making minor or patch changes. Copied directly from react-art with requires fixed. (I also picked a different haste name just in case.)
2016-05-15 06:30:08 +08:00
"art": "^0.10.1",
Add coveralls.
2015-12-22 04:05:03 +08:00
"async": "^1.5.0",
[docs] Upgrade to work with babel 6, fetch remote babel-browser for now
2016-03-08 02:37:06 +08:00
"babel-cli": "^6.6.5",
Update to Babel 6
2016-02-27 08:49:32 +08:00
"babel-core": "^6.0.0",
"babel-eslint": "^5.0.0",
"babel-plugin-check-es2015-constants": "^6.5.0",
"babel-plugin-syntax-trailing-function-commas": "^6.5.0",
upgraded babel-plugin-transform-class-properties - babel/babel#3589 fixed inferring class name
2016-07-24 05:53:59 +08:00
"babel-plugin-transform-class-properties": "^6.11.5",
Update to Babel 6
2016-02-27 08:49:32 +08:00
"babel-plugin-transform-es2015-arrow-functions": "^6.5.2",
"babel-plugin-transform-es2015-block-scoped-functions": "^6.5.0",
"babel-plugin-transform-es2015-block-scoping": "^6.5.0",
"babel-plugin-transform-es2015-classes": "^6.5.2",
"babel-plugin-transform-es2015-computed-properties": "^6.5.2",
"babel-plugin-transform-es2015-destructuring": "^6.5.0",
"babel-plugin-transform-es2015-for-of": "^6.5.2",
"babel-plugin-transform-es2015-literals": "^6.5.0",
"babel-plugin-transform-es2015-modules-commonjs": "^6.5.2",
"babel-plugin-transform-es2015-object-super": "^6.5.0",
"babel-plugin-transform-es2015-parameters": "^6.5.0",
"babel-plugin-transform-es2015-shorthand-properties": "^6.5.0",
"babel-plugin-transform-es2015-spread": "^6.5.2",
"babel-plugin-transform-es2015-template-literals": "^6.5.2",
"babel-plugin-transform-es3-member-expression-literals": "^6.5.0",
"babel-plugin-transform-es3-property-literals": "^6.5.0",
Add Object Spread Support to Our Babel Config Won't really use this in prod code yet but I have a benchmark that uses it.
2016-03-25 07:26:34 +08:00
"babel-plugin-transform-object-rest-spread": "^6.6.5",
fixed transform-react-jsx-source devDep (#6697)
2016-05-04 14:50:27 +08:00
"babel-plugin-transform-react-jsx-source": "^6.8.0",
Update to Babel 6
2016-02-27 08:49:32 +08:00
"babel-preset-react": "^6.5.0",
Add a gulp script for extracting error codes (#6882)
2016-06-02 02:21:26 +08:00
"babel-traverse": "^6.9.0",
pinned babylon version for eslint to work (#7008)
2016-06-10 07:14:44 +08:00
"babylon": "6.8.0",
Upgrade browserify
2016-04-06 01:53:53 +08:00
"browserify": "^13.0.0",
use bundle-collapser to reduce browserified file size
2014-12-31 14:57:47 +08:00
"bundle-collapser": "^1.1.1",
Add CoffeeScript Class Test As part of the new class effort it is now possible to define React Components using any type of generic JavaScript class syntax. This includes CoffeeScript. This test ensures that we don't regress that support, and also serves as an example for using React in CoffeeScript. This test fail trails the ReactES6Class-test file. Some manual tweaking is required when converting tests.
2015-01-26 18:19:35 +08:00
"coffee-script": "^1.8.0",
devDependencies: add core-js and es6-symbol polyfill for tests
2016-04-02 20:26:35 +08:00
"core-js": "^2.2.1",
Add coveralls.
2015-12-22 04:05:03 +08:00
"coveralls": "^2.11.6",
update deps
2015-11-12 21:02:45 +08:00
"del": "^2.0.2",
update deps
2015-10-27 06:15:00 +08:00
"derequire": "^2.0.3",
Update lint config, dependencies, fix issues This also fixes messages from new synthetic events warnings
2016-03-03 07:07:45 +08:00
"eslint": "1.10.3",
"eslint-plugin-react": "4.1.0",
Load custom eslint rules as plugin, w/o --rulesdir This allows us to load the eslint rules without requiring command-line arguments, which avoids breaking editors with eslint plugins. https://github.com/eslint/eslint/issues/2180#issuecomment-87722150
2015-06-05 08:04:45 +08:00
"eslint-plugin-react-internal": "file:eslint-rules",
Upgrade to fbjs v0.8.4 (#7532)
2016-08-20 01:40:03 +08:00
"fbjs": "^0.8.4",
Upgrade fbjs
2016-04-06 01:50:54 +08:00
"fbjs-scripts": "^0.6.0",
Apply side-effects to host containers This updates the host container root with new children. Currently, this is always called for updates because we don't track if any children reordered.
2016-06-30 15:58:43 +08:00
"flow-bin": "^0.27.0",
Add coveralls.
2015-12-22 04:05:03 +08:00
"glob": "^6.0.1",
More conservative dependency update.
2015-06-27 09:37:15 +08:00
"grunt": "^0.4.5",
Use local `grunt` executable on Travis Builds have been flaky lately. Maybe this will help?
2015-04-23 04:00:42 +08:00
"grunt-cli": "^0.1.13",
More conservative dependency update.
2015-06-27 09:37:15 +08:00
"grunt-compare-size": "^0.4.0",
Update dependencies, removed unused ones Also picked up a bit of JSON reformatting, presumably from npm >= 2 Test plan: build, run tests
2014-10-01 06:22:17 +08:00
"grunt-contrib-clean": "^0.6.0",
update deps
2015-10-27 06:15:00 +08:00
"grunt-contrib-compress": "^0.14.0",
Use fbjs package from npm, gulp This reworks a few things in building and distributing React. The biggest change is using fbjs to share dependencies with other libraries. We're also using Gulp for some build steps.
2015-07-18 09:20:38 +08:00
"gulp": "^3.9.0",
Update to Babel 6
2016-02-27 08:49:32 +08:00
"gulp-babel": "^6.0.0",
update deps
2015-10-27 06:15:00 +08:00
"gulp-flatten": "^0.2.0",
Gulp: lint, flow, and version-check (#7174) * Add plugin loading for gulp * Convert `lint` task to gulp * Convert `flow` task to gulp * Convert `version-check` task to gulp * Add missing semicolons
2016-07-06 04:30:09 +08:00
"gulp-load-plugins": "^1.2.4",
Add a gulp script for extracting error codes (#6882)
2016-06-02 02:21:26 +08:00
"gulp-util": "^3.0.7",
Minify both before and after browserify
2013-12-29 14:41:54 +08:00
"gzip-js": "~0.3.2",
jest@12.1.1
2016-05-21 04:51:04 +08:00
"jest": "^12.1.1",
Use loose-envify instead of envify This reduces the number of transitive dependencies and decreases the build time (by ~6% on my machine).
2016-03-20 06:28:50 +08:00
"loose-envify": "^1.1.0",
Build renderers into their individual npm packages (#7168) This copies modules into three separate packages instead of putting it all in React. The overlap in shared and between renderers gets duplicated. This allows the isomorphic package to stay minimal. It can also be used as a direct dependency without much risk. This also allow us to ship versions to each renderer independently and we can ship renderers without updating the main react package dependency.
2016-08-11 09:17:49 +08:00
"merge-stream": "^1.0.0",
Ensure we're using latest object-assign (#6681) This picks up the change to feature test against order bugs.
2016-05-03 04:16:25 +08:00
"object-assign": "^4.1.0",
Update many npm dependencies Sauce/connect related things need some more work and I didn't want to figure those out right now. Fixes #1701
2014-06-18 05:21:24 +08:00
"platform": "^1.1.0",
update deps
2015-10-27 06:15:00 +08:00
"run-sequence": "^1.1.4",
Use fbjs package from npm, gulp This reworks a few things in building and distributing React. The biggest change is using fbjs to share dependencies with other libraries. We're also using Gulp for some build steps.
2015-07-18 09:20:38 +08:00
"through2": "^2.0.0",
update deps
2015-10-27 06:15:00 +08:00
"tmp": "~0.0.28",
update typescript
2016-05-03 07:08:12 +08:00
"typescript": "~1.8.10",
update deps
2015-10-27 06:15:00 +08:00
"uglify-js": "^2.5.0",
Remove in-browser unit testing Rely on jest for now until we get a better and less hacky solution to running tests in the browser, probably a totally different test suite with different behavior/goals.
2015-07-16 09:58:51 +08:00
"uglifyify": "^3.0.1"
Initial public release
2013-05-30 03:46:11 +08:00
},
Check for compatible node,npm versions on install This is only for building React and doesnn't apply to production installs.
2015-08-19 09:05:13 +08:00
"devEngines": {
package(node-engine-version): accept 6.x versions (#6645)
2016-04-29 02:33:26 +08:00
"node": "4.x || 5.x || 6.x",
add npm 3.x to devengines
2015-10-13 16:06:48 +08:00
"npm": "2.x || 3.x"
Recommend Node v0.10.0 due to https://github.com/isaacs/npm/issues/2907
2013-06-28 04:09:29 +08:00
},
s/jsxConfig/commonerConfig/g
2013-12-05 05:47:13 +08:00
"commonerConfig": {
Better invariant / warning replacement
2015-05-22 10:08:18 +08:00
"version": 7
Add support for `npm test`
2014-02-21 05:10:05 +08:00
},
"scripts": {
Upgrade babel, babel-eslint; remove babel-core dep
2015-07-22 07:59:25 +08:00
"build": "grunt build",
npm script to run lint only on changed files
2015-06-16 16:16:59 +08:00
"linc": "git diff --name-only --diff-filter=ACMRTUB `git merge-base HEAD master` | grep '\\.js$' | xargs eslint --",
Upgrade babel, babel-eslint; remove babel-core dep
2015-07-22 07:59:25 +08:00
"lint": "grunt lint",
Upgrade to fbjs, fbjs-scripts @ 0.2
2015-09-01 08:17:30 +08:00
"postinstall": "node node_modules/fbjs-scripts/node/check-dev-engines.js package.json",
[flow] annotate accumulate and accumulateInto Summary: Trying to start adding flow types to files in React. I needed to add a script to package.json in order to run flow, flow-bin is already a dependency. I had to rewrite the implementation a bit. Flow doesn't recognize ``` var currentIsArray = Array.isArray(current); if (currentIsArray) { // not refined } ``` but the following does work ``` if (Array.isArray(current)) { // refined } ``` Test Plan: npm run-script flow npm run-script test accumulate Reviewers: @zpao @spicyj
2016-06-16 23:18:30 +08:00
"test": "jest",
"flow": "flow"
Add configuration for running tests with Jest Can be run with `node_modules/.bin/jest` for now; didn't want to disturb the grunt setup. Right now one test fails with: ``` FAIL browser/ui/__tests__/ReactDOMComponent-test.js (1.423s) ● ReactDOMComponent › updateDOM › it should update styles when mutating style object - Expected: '0' toEqual: '0.5' at Spec.<anonymous> (src/browser/ui/__tests__/ReactDOMComponent-test.js:99:33) ``` which I can only assume is a jsdom problem -- no other asserts fail.
2014-05-13 15:40:29 +08:00
},
"jest": {
Upgrade babel, babel-eslint; remove babel-core dep
2015-07-22 07:59:25 +08:00
"modulePathIgnorePatterns": [
"/.module-cache/",
"/react/build/"
],
"persistModuleRegistryBetweenSpecs": true,
Include vendor/ when running jest tests Now the two transform tests get run alongside the React core tests. Test Plan: jest
2014-08-30 16:08:57 +08:00
"rootDir": "",
Use fbjs package from npm, gulp This reworks a few things in building and distributing React. The biggest change is using fbjs to share dependencies with other libraries. We're also using Gulp for some build steps.
2015-07-18 09:20:38 +08:00
"scriptPreprocessor": "scripts/jest/preprocessor.js",
"setupEnvScriptFile": "scripts/jest/environment.js",
Fail jest tests on any un-spied warnings Originally #4223 -- we lost this when we switched to jest.
2015-09-30 08:35:39 +08:00
"setupTestFrameworkScriptFile": "scripts/jest/test-framework-setup.js",
Add CoffeeScript Class Test As part of the new class effort it is now possible to define React Components using any type of generic JavaScript class syntax. This includes CoffeeScript. This test ensures that we don't regress that support, and also serves as an example for using React in CoffeeScript. This test fail trails the ReactES6Class-test file. Some manual tweaking is required when converting tests.
2015-01-26 18:19:35 +08:00
"testFileExtensions": [
Add Basic TypeScript Class Test As part of the new class effort it is now possible to define React Components using any type of generic JavaScript class syntax. This includes TypeScript classes. This test ensures that we don't regress that support, and also serves as an example for using React in TypeScript. TypeScript provides a good demo of where we think property initializers are going. We don't have any official *type* support for TypeScript yet. This test trails the ReactES6Class-test file. Some manual tweaking is required when converting tests.
2015-01-27 08:59:11 +08:00
"coffee",
Upgrade babel, babel-eslint; remove babel-core dep
2015-07-22 07:59:25 +08:00
"js",
Add Basic TypeScript Class Test As part of the new class effort it is now possible to define React Components using any type of generic JavaScript class syntax. This includes TypeScript classes. This test ensures that we don't regress that support, and also serves as an example for using React in TypeScript. TypeScript provides a good demo of where we think property initializers are going. We don't have any official *type* support for TypeScript yet. This test trails the ReactES6Class-test file. Some manual tweaking is required when converting tests.
2015-01-27 08:59:11 +08:00
"ts"
Add CoffeeScript Class Test As part of the new class effort it is now possible to define React Components using any type of generic JavaScript class syntax. This includes CoffeeScript. This test ensures that we don't regress that support, and also serves as an example for using React in CoffeeScript. This test fail trails the ReactES6Class-test file. Some manual tweaking is required when converting tests.
2015-01-26 18:19:35 +08:00
],
Only run src/ and vendor/fbtransform/ tests in jest Test Plan: jest
2015-03-26 07:48:43 +08:00
"testPathDirs": [
Upgrade babel, babel-eslint; remove babel-core dep
2015-07-22 07:59:25 +08:00
"<rootDir>/eslint-rules",
Remove `generateFromMetadata` and `getMetadata` usage.
2015-10-29 14:38:29 +08:00
"<rootDir>/mocks",
Add a gulp script for extracting error codes (#6882)
2016-06-02 02:21:26 +08:00
"<rootDir>/scripts",
Use fbjs package from npm, gulp This reworks a few things in building and distributing React. The biggest change is using fbjs to share dependencies with other libraries. We're also using Gulp for some build steps.
2015-07-18 09:20:38 +08:00
"<rootDir>/src",
"node_modules/fbjs"
Update dependencies, removed unused ones Also picked up a bit of JSON reformatting, presumably from npm >= 2 Test plan: build, run tests
2014-10-01 06:22:17 +08:00
],
"unmockedModulePathPatterns": [
""
]
Establish a convention for forcing jsx rebuilds. Pull request #526 updated the behavior of vendor/constants.js without changing any source files or the bin/jsx-internal script, so files that should have been rebuilt (like utils/__tests__/ImmutableObject-test.js) were not automatically rebuilt (unless you knew to do `grunt clean` or `rm -rf .module-cache` manually). This commit allows us to bump a version number when we know the transform toolchain has been altered in a way that will not be visible to commoner/jsx. With this convention, if we reset to an older revision (e.g. during a git bisect) and the appropriate cached module files are still in the .module-cache/, they can be used without rebuilding. That's why I prefer this approach to just deleting the .module-cache/. Closes #104. Closes #496. Closes #530.
2013-11-14 07:02:23 +08:00
}
Initial public release
2013-05-30 03:46:11 +08:00
}