OSSForks/react
1
0
Fork 0
mirror of https://github.com/zebrajr/react.git synced 2026-01-15 12:15:22 +00:00
Code Issues Actions 6 Packages Projects Releases Wiki Activity
Files
bffed177f4776efe7c77f38bd9ff1836d3136493
react/package.json

81 lines
2.1 KiB
JSON
Raw Normal View History

Initial public release
2013-05-29 12:46:11 -07: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-02 14:13:11 -07:00
"name": "react-build",
"private": true,
Bump version in master for 0.15 development
2015-10-07 09:57:53 -07:00
"version": "0.15.0-alpha",
Initial public release
2013-05-29 12:46:11 -07:00
"devDependencies": {
Upgrade babel, babel-eslint; remove babel-core dep
2015-07-21 16:59:25 -07:00
"babel": "^5.8.3",
[lint] Update and fix
2015-09-25 12:32:51 -07:00
"babel-eslint": "^4.1.3",
More conservative dependency update.
2015-06-26 18:37:15 -07:00
"benchmark": "^1.0.0",
Update dependencies
2015-02-22 12:58:41 -08:00
"browserify": "^9.0.3",
use bundle-collapser to reduce browserified file size
2014-12-30 22: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 02:19:35 -08:00
"coffee-script": "^1.8.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-17 18:20:38 -07:00
"del": "^1.2.0",
Update to derequire@^2.0.0
2015-03-08 23:43:47 -04:00
"derequire": "^2.0.0",
Update dependencies, removed unused ones Also picked up a bit of JSON reformatting, presumably from npm >= 2 Test plan: build, run tests
2014-09-30 15:22:17 -07:00
"envify": "^3.0.0",
[lint] Update and fix
2015-09-25 12:32:51 -07:00
"eslint": "^1.5.1",
"eslint-plugin-react": "^3.4.2",
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-04 17:04:45 -07:00
"eslint-plugin-react-internal": "file:eslint-rules",
Update to fbjs@0.3 As far as we're concerned, the only difference is that we moved some files from React to fbjs.
2015-10-01 14:29:07 -07:00
"fbjs": "^0.3.1",
Upgrade to fbjs, fbjs-scripts @ 0.2
2015-08-31 17:17:30 -07:00
"fbjs-scripts": "^0.2.0",
More conservative dependency update.
2015-06-26 18:37:15 -07:00
"grunt": "^0.4.5",
Use local `grunt` executable on Travis Builds have been flaky lately. Maybe this will help?
2015-04-22 13:00:42 -07:00
"grunt-cli": "^0.1.13",
More conservative dependency update.
2015-06-26 18:37:15 -07: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-09-30 15:22:17 -07:00
"grunt-contrib-clean": "^0.6.0",
Update package deps
2015-01-13 11:23:06 -08:00
"grunt-contrib-compress": "^0.13.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-17 18:20:38 -07:00
"gulp": "^3.9.0",
"gulp-babel": "^5.1.0",
"gulp-flatten": "^0.1.0",
"gulp-util": "^3.0.5",
Minify both before and after browserify
2013-12-28 23:41:54 -07:00
"gzip-js": "~0.3.2",
Upgrade to node@4, jest@0.5
2015-08-18 23:40:32 -07:00
"jest-cli": "^0.5.7",
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-02 14:13:11 -07:00
"jstransform": "^11.0.0",
Finish addons packaging - Add missing object-assign dependency - Add batchedUpdates to ReactDOMClient, rename the two addons to `unstable_` - Delete react/addons/* (leaving react/addons with a slightly updated warning) - Add README.md, LICENSE, PATENTS to each addons package
2015-07-02 23:26:47 +02:00
"object-assign": "^3.0.0",
More conservative dependency update.
2015-06-26 18:37:15 -07:00
"optimist": "^0.6.1",
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-17 14:21:24 -07:00
"platform": "^1.1.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-17 18:20:38 -07:00
"run-sequence": "^1.1.0",
"through2": "^2.0.0",
Provide `grunt npm:test` for verifying NPM package functionality. This basically calls `npm pack`, installs the resulting package in a temporary directory, then requires it and attempts to use the .transform method. Closes #12.
2013-05-30 10:42:01 -04:00
"tmp": "~0.0.18",
Lock typescript dep at 1.4
2015-07-23 12:49:21 -07:00
"typescript": "~1.4.0",
More conservative dependency update.
2015-06-26 18:37:15 -07:00
"uglify-js": "^2.4.23",
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-15 18:58:51 -07:00
"uglifyify": "^3.0.1"
Initial public release
2013-05-29 12:46:11 -07:00
},
Check for compatible node,npm versions on install This is only for building React and doesnn't apply to production installs.
2015-08-18 18:05:13 -07:00
"devEngines": {
Upgrade to node@4, jest@0.5
2015-08-18 23:40:32 -07:00
"node": "4.x",
Check for compatible node,npm versions on install This is only for building React and doesnn't apply to production installs.
2015-08-18 18:05:13 -07:00
"npm": "2.x"
Recommend Node v0.10.0 due to https://github.com/isaacs/npm/issues/2907
2013-06-27 13:09:29 -07:00
},
s/jsxConfig/commonerConfig/g
2013-12-04 16:47:13 -05:00
"commonerConfig": {
Better invariant / warning replacement
2015-05-21 19:08:18 -07:00
"version": 7
Add support for `npm test`
2014-02-20 13:10:05 -08:00
},
"scripts": {
Upgrade babel, babel-eslint; remove babel-core dep
2015-07-21 16:59:25 -07:00
"build": "grunt build",
npm script to run lint only on changed files
2015-06-16 01:16:59 -07: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-21 16:59:25 -07:00
"lint": "grunt lint",
Upgrade to fbjs, fbjs-scripts @ 0.2
2015-08-31 17:17:30 -07:00
"postinstall": "node node_modules/fbjs-scripts/node/check-dev-engines.js package.json",
Enforce NODE_ENV=test You could make the argument that this should be optional, but it doesn't work without it so we might as well just enforce it. Makes `jest` work by default.
2015-09-30 17:43:06 -07:00
"test": "jest"
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 00:40:29 -07:00
},
"jest": {
Upgrade babel, babel-eslint; remove babel-core dep
2015-07-21 16:59:25 -07: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 01:08:57 -07: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-17 18:20:38 -07: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-29 17:35:39 -07: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 02: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-26 16:59:11 -08:00
"coffee",
Upgrade babel, babel-eslint; remove babel-core dep
2015-07-21 16:59:25 -07: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-26 16: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 02:19:35 -08:00
],
Only run src/ and vendor/fbtransform/ tests in jest Test Plan: jest
2015-03-25 16:48:43 -07:00
"testPathDirs": [
Upgrade babel, babel-eslint; remove babel-core dep
2015-07-21 16:59:25 -07:00
"<rootDir>/eslint-rules",
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-17 18:20:38 -07: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-09-30 15:22:17 -07: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-13 18:02:23 -05:00
}
Initial public release
2013-05-29 12:46:11 -07:00
}
Reference in New Issue Copy Permalink