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

103 lines
2.3 KiB
JSON
Raw Normal View History

Initial public release
2013-05-30 03:46:11 +08: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-20 03:34:03 +08:00
"description": "A set of complementary tools to React, including the JSX transformer.",
v0.13.0-alpha.2
2015-01-14 03:35:53 +08:00
"version": "0.13.0-alpha.2",
Initial public release
2013-05-30 03:46:11 +08:00
"keywords": [
v0.3.2 Also some tweaks to package.json details.
2013-06-01 07:52:38 +08:00
"react",
"jsx",
"transformer",
"view"
Initial public release
2013-05-30 03:46:11 +08:00
],
v0.3.2 Also some tweaks to package.json details.
2013-06-01 07:52:38 +08:00
"homepage": "http://facebook.github.io/react",
Initial public release
2013-05-30 03:46:11 +08:00
"bugs": "https://github.com/facebook/react/issues",
BSD + PATENTS
2014-10-09 08:27:59 +08:00
"license": "BSD-3-Clause",
Initial public release
2013-05-30 03:46:11 +08:00
"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-23 13:25:23 +08: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-04 08:39:33 +08:00
"vendor/fbtransform/"
Initial public release
2013-05-30 03:46:11 +08: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-19 06:11:02 +08:00
"commoner": "^0.10.0",
Update stripTypes transform to use fixed up jstransform transform
2014-11-15 09:58:51 +08:00
"jstransform": "^8.0.0"
Initial public release
2013-05-30 03:46:11 +08:00
},
"devDependencies": {
benchmark runner
2013-12-17 13:25:05 +08:00
"benchmark": "~1.0.0",
Update package deps
2015-01-14 03:23:06 +08:00
"browserify": "^8.1.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",
Update other dependencies
2014-01-17 03:42:48 +08:00
"coverify": "~1.0.4",
browserify update
2014-10-01 11:31:36 +08:00
"derequire": "^1.2.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
"envify": "^3.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-16 08: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-13 10:09:00 +08:00
"es5-shim": "^4.0.0",
Use eslint These rules are very close to what we have internally. We may still miss a couple things (jsdoc params being a big one) but it's good enough. This is also more restrictive than what we enforce internally, but it's for the best.
2014-12-05 08:21:43 +08:00
"eslint": "0.11.0-alpha.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-18 01:33:09 +08:00
"grunt": "~0.4.2",
Minify both before and after browserify
2013-12-29 14:41:54 +08:00
"grunt-cli": "~0.1.9",
"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 package deps
2015-01-14 03:23:06 +08:00
"grunt-contrib-compress": "^0.13.0",
Update other dependencies
2014-01-17 03:42:48 +08:00
"grunt-contrib-connect": "~0.6.0",
Update NPM dependencies This was mostly to update Jest, but the others were the safe ones from `npm outdated --depth=0`
2014-12-17 06:04:15 +08:00
"grunt-contrib-copy": "^0.7.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
"grunt-contrib-jshint": "^0.10.0",
Minify both before and after browserify
2013-12-29 14:41:54 +08:00
"gzip-js": "~0.3.2",
"jasmine-tapreporter": "~0.2.2",
Update NPM dependencies This was mostly to update Jest, but the others were the safe ones from `npm outdated --depth=0`
2014-12-17 06:04:15 +08:00
"jest-cli": "^0.2.1",
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-18 01:33:09 +08:00
"lodash": "~2.4.1",
Update package dependencies Sometimes I look at https://david-dm.org/facebook/react
2013-08-28 05:46:06 +08:00
"optimist": "~0.6.0",
making phantomjs version less specific
2013-11-07 06:00:25 +08: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-18 05:21:24 +08:00
"platform": "^1.1.0",
Minify both before and after browserify
2013-12-29 14:41:54 +08:00
"populist": "~0.1.6",
Update NPM dependencies This was mostly to update Jest, but the others were the safe ones from `npm outdated --depth=0`
2014-12-17 06:04:15 +08:00
"recast": "^0.9.11",
Minify both before and after browserify
2013-12-29 14:41:54 +08:00
"sauce-tunnel": "~1.1.0",
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-compiler": "^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 22:42:01 +08:00
"tmp": "~0.0.18",
Minify both before and after browserify
2013-12-29 14:41:54 +08: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-18 05:21:24 +08:00
"uglifyify": "^2.4.0",
Minify both before and after browserify
2013-12-29 14:41:54 +08:00
"wd": "~0.2.6"
Initial public release
2013-05-30 03:46:11 +08:00
},
Recommend Node v0.10.0 due to https://github.com/isaacs/npm/issues/2907
2013-06-28 04:09:29 +08: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-14 07:02:23 +08:00
"preferGlobal": true,
s/jsxConfig/commonerConfig/g
2013-12-05 05:47:13 +08:00
"commonerConfig": {
Strip calls to warning() in __DEV__ Fixes #1120.
2014-02-18 09:28:38 +08:00
"version": 4
Add support for `npm test`
2014-02-21 05:10:05 +08:00
},
"scripts": {
Use jest for `npm test` I've given in and this is easier than `npm run jest`. `grunt test` still exists and is used by Travis so this has no CI implications.
2014-11-26 07:07:46 +08:00
"test": "jest",
Use eslint These rules are very close to what we have internally. We may still miss a couple things (jsdoc params being a big one) but it's good enough. This is also more restrictive than what we enforce internally, but it's for the best.
2014-12-05 08:21:43 +08:00
"jest": "jest",
Add `npm run build` It's a "shortcut" to `grunt build`
2015-01-22 09:22:31 +08:00
"lint": "eslint src",
"build": "grunt build"
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": {
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": "",
"scriptPreprocessor": "jest/preprocessor.js",
"setupEnvScriptFile": "jest/environment.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": [
"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
"coffee",
"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
],
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
"modulePathIgnorePatterns": [
"/build/",
"/node_modules/",
"/.module-cache/"
],
"testPathIgnorePatterns": [
"/build/",
"/node_modules/"
],
"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
}