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
4af98990db0e7f7995b2e1c63d04497da9de296c
react/package.json

90 lines
2.0 KiB
JSON
Raw Normal View History

Initial public release
2013-05-29 12:46:11 -07:00
{
"name": "react-tools",
Add descriptions to package.jsons Otherwise, npm just reads the first non-header of our readmes, which doesn't match up accurately or cleanly (no markdown parsing).
2014-02-19 11:34:03 -08:00
"description": "A set of complementary tools to React, including the JSX transformer.",
Bump version for 0.12.0-alpha [skip ci]
2014-07-17 14:22:22 -07:00
"version": "0.12.0-alpha",
Initial public release
2013-05-29 12:46:11 -07:00
"keywords": [
v0.3.2 Also some tweaks to package.json details.
2013-05-31 16:52:38 -07:00
"react",
"jsx",
"transformer",
"view"
Initial public release
2013-05-29 12:46:11 -07:00
],
v0.3.2 Also some tweaks to package.json details.
2013-05-31 16:52:38 -07:00
"homepage": "http://facebook.github.io/react",
Initial public release
2013-05-29 12:46:11 -07:00
"bugs": "https://github.com/facebook/react/issues",
"licenses": [
{
"type": "Apache-2.0",
"url": "http://www.apache.org/licenses/LICENSE-2.0"
}
],
"files": [
"main.js",
"bin/jsx",
[react-tools] Add src/ to files This is so it's possible to use the original @providesModule source files in a toolchain that understands those.
2013-08-22 22:25:23 -07:00
"src/",
Custom readme for react-tools Of course this means I can no longer just npm publish from the project root, but I haven't been anyway.
2014-07-03 17:39:33 -07:00
"vendor/fbtransform/"
Initial public release
2013-05-29 12:46:11 -07:00
],
"main": "main.js",
"bin": {
"jsx": "./bin/jsx"
},
"repository": {
"type": "git",
"url": "https://github.com/facebook/react"
},
"dependencies": {
Upgrade Commoner It no longer parses @providesModule directives by default. Fixes #1145
2014-08-18 15:11:02 -07:00
"commoner": "^0.10.0",
Bump dependencies that are known safe Most of these would have been installed anyway, just making sure what got shrinkwrapped is what others would experience.
2014-07-12 19:09:00 -07:00
"esprima-fb": "^4001.3001.0-dev-harmony-fb",
"jstransform": "^6.0.1"
Initial public release
2013-05-29 12:46:11 -07:00
},
"devDependencies": {
benchmark runner
2013-12-17 00:25:05 -05:00
"benchmark": "~1.0.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-17 14:21:24 -07:00
"browserify": "^4.1.10",
Update other dependencies
2014-01-16 11:42:48 -08:00
"coverify": "~1.0.4",
Update npm dependencies [skip ci]
2014-07-03 09:56:42 -07:00
"envify": "^2.0.0",
Run es3ify over unminified builds Makes no difference to react.js and react-with-addons.js; quotes .static in four places for JSXTransformer.js: https://gist.github.com/spicyj/aada5352e813752a4667
2014-02-15 16:32:36 -08:00
"es3ify": "~0.1.2",
Bump dependencies that are known safe Most of these would have been installed anyway, just making sure what got shrinkwrapped is what others would experience.
2014-07-12 19:09:00 -07:00
"es5-shim": "^4.0.0",
Upgrade (explicitly) grunt They deprecated the use of some packaged modules and suggest using those modules directly. http://gruntjs.com/blog/2013-11-21-grunt-0.4.2-released Lodash was the only use we had.
2014-01-17 09:33:09 -08:00
"grunt": "~0.4.2",
Minify both before and after browserify
2013-12-28 23:41:54 -07:00
"grunt-cli": "~0.1.9",
"grunt-compare-size": "~0.4.0",
"grunt-contrib-clean": "~0.5.0",
Update npm dependencies [skip ci]
2014-07-03 09:56:42 -07:00
"grunt-contrib-compress": "^0.9.1",
Update other dependencies
2014-01-16 11:42:48 -08:00
"grunt-contrib-connect": "~0.6.0",
"grunt-contrib-copy": "~0.5.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-17 14:21:24 -07:00
"grunt-contrib-jshint": "^0.10.0",
Minify both before and after browserify
2013-12-28 23:41:54 -07:00
"gzip-js": "~0.3.2",
"jasmine-tapreporter": "~0.2.2",
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-cli": "~0.1.5",
Upgrade (explicitly) grunt They deprecated the use of some packaged modules and suggest using those modules directly. http://gruntjs.com/blog/2013-11-21-grunt-0.4.2-released Lodash was the only use we had.
2014-01-17 09:33:09 -08:00
"lodash": "~2.4.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
"microtime": "^0.6.0",
Update package dependencies Sometimes I look at https://david-dm.org/facebook/react
2013-08-27 14:46:06 -07:00
"optimist": "~0.6.0",
making phantomjs version less specific
2013-11-06 17:00:25 -05:00
"phantomjs": "~1.9",
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",
Minify both before and after browserify
2013-12-28 23:41:54 -07:00
"populist": "~0.1.6",
Update recast to 0.6, update constants.js I dropped the part of constants.js that we weren't using (namely the part where we insert constants) but left it open to do that. It should be trivial, we just aren't using it. Fixes #1824
2014-08-14 11:11:17 -07:00
"recast": "^0.6.10",
Minify both before and after browserify
2013-12-28 23:41:54 -07:00
"sauce-tunnel": "~1.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-17 14:21:24 -07:00
"semver": "^2.3.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",
Minify both before and after browserify
2013-12-28 23:41:54 -07:00
"uglify-js": "~2.4.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-17 14:21:24 -07:00
"uglifyify": "^2.4.0",
Minify both before and after browserify
2013-12-28 23:41:54 -07:00
"wd": "~0.2.6"
Initial public release
2013-05-29 12:46:11 -07:00
},
Recommend Node v0.10.0 due to https://github.com/isaacs/npm/issues/2907
2013-06-27 13:09:29 -07:00
"engines": {
"node": ">=0.10.0"
},
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
"preferGlobal": true,
s/jsxConfig/commonerConfig/g
2013-12-04 16:47:13 -05:00
"commonerConfig": {
Strip calls to warning() in __DEV__ Fixes #1120.
2014-02-17 17:28:38 -08:00
"version": 4
Add support for `npm test`
2014-02-20 13:10:05 -08:00
},
"scripts": {
Make `npm run-script jest` available This is slightly shorter than typing `./node_modules/.bin/jest`.
2014-08-20 11:48:01 -07:00
"test": "./node_modules/.bin/grunt test",
"jest": "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": {
"rootDir": "src",
"scriptPreprocessor": "../jest/preprocessor.js",
"setupEnvScriptFile": "../jest/environment.js",
"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