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.",
0.14.0-alpha3
2015-05-28 07:47:35 +08:00
"version": "0.14.0-alpha3",
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
],
SSL/TLSize all the things! (convert http:// to https:// where appropriate) Update links to use https:// where it is supported. There's probably a lot more that could be fixed, but these are the core ones I found (especially the download links in order to prevent MITM attacks). Note that there are some fb.me links that will redirect to http:// even while accessed over https://, but this seemed like the best way to fix those for now. NOTE: Only non-third-party files were modified. There are references to http:// URLs in vendored/third-party files, but seems appropriate to fix upstream for those rather than editing the files. Also, copy one image locally to the blog, as it was hotlinking to a site that did not support https://. Last, use youtube-nocookie.com instead of youtube.com for video embeds, as the former doesn't try to set a cookie on load (privacy enhancement).
2015-04-19 06:41:56 +08:00
"homepage": "https://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",
Remove transforms from repo, react-tools Time to just use jstransform.
2015-04-29 06:14:42 +08:00
"src/"
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",
Remove transforms from repo, react-tools Time to just use jstransform.
2015-04-29 06:14:42 +08:00
"jstransform": "^11.0.0"
Initial public release
2013-05-30 03:46:11 +08:00
},
"devDependencies": {
Update eslint-related dependencies - babel-eslint ^3.1.14 fixes babel/babel-eslint#120 - babel updated from ^5.3.3 to ^3.5.5, which changes stuff, I guess - eslint updated from ^0.21.2 to ^0.22.1, which makes `no-shadow` also check class declarations
2015-06-06 01:18:38 +08:00
"babel": "^5.5.5",
"babel-eslint": "^3.1.14",
benchmark runner
2013-12-17 13:25:05 +08:00
"benchmark": "~1.0.0",
Update dependencies
2015-02-23 04:58:41 +08:00
"browserify": "^9.0.3",
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",
Update to derequire@^2.0.0
2015-03-09 11:43:47 +08: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-10-01 06:22:17 +08:00
"envify": "^3.0.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-13 10:09:00 +08:00
"es5-shim": "^4.0.0",
Update eslint-related dependencies - babel-eslint ^3.1.14 fixes babel/babel-eslint#120 - babel updated from ^5.3.3 to ^3.5.5, which changes stuff, I guess - eslint updated from ^0.21.2 to ^0.22.1, which makes `no-shadow` also check class declarations
2015-06-06 01:18:38 +08:00
"eslint": "^0.22.1",
Enable react/wrap-multilines eslint rule Multiline jsx literals in a return should be paren-wrapped.
2015-06-03 01:43:42 +08:00
"eslint-plugin-react": "^2.5.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",
Add custom eslint rule for warning and invariant See #2869 Checks that the *second* argument of warning and invariant are a literal string, or a concatination of literal strings, and that the number of arguments is correct based on the number of %s substrings. This commit also fixes a few places where the existing code had broken error messages! The rule itself is pretty straightforward, although adding the tests ended up being a bit painful, as eslint-tester depends on mocha, and therefore needs to be run in a separate grunt task.
2015-06-04 06:09:50 +08:00
"eslint-tester": "^0.7.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",
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",
Minify both before and after browserify
2013-12-29 14:41:54 +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 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",
Run jest with grunt, add to travis This is to make sure we don't end up with differences in our different testing methods. We may switch out the failure allowances later (maybe just jest will be good enough and we can let phantom fail for a little bit).
2015-01-28 09:59:05 +08:00
"grunt-jest": "^0.1.2",
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 jest to latest
2015-06-12 02:01:00 +08:00
"jest-cli": "^0.4.11",
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",
"sauce-tunnel": "~1.1.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",
Use TypeScript Compiler API Directly In 1.4.0 we can use the TypeScript API directly to preprocess our files. This lets us get rid of a dependency. https://github.com/Microsoft/TypeScript/wiki/Using-the-Compiler-API We can also use this to provide our default libraries so that we don't need to keep the references in the test file.
2015-02-02 14:41:00 +08:00
"typescript": "^1.4.0",
Update uglify dependency Apparently we needed to get to v2.4.17 to get the fix for #2247. We shrinkwrapped on the same day but the timing didn't work out so we missed it.
2015-04-14 03:49:45 +08:00
"uglify-js": "^2.4.20",
Update dependencies
2015-02-23 04:58:41 +08:00
"uglifyify": "^3.0.1",
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": {
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": {
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",
Fix `npm run lint` Broke in #4021.
2015-06-05 04:20:42 +08:00
"lint": "grunt lint",
Add `npm run build` It's a "shortcut" to `grunt build`
2015-01-22 09:22:31 +08:00
"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",
[jest] Use persistModuleRegistryBetweenSpecs This more closely matches how we have jest configured at FB, so when we pull in and run internally we will have fewer things to waste time on.
2015-01-28 11:17:31 +08:00
"persistModuleRegistryBetweenSpecs": true,
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/"
],
Only run src/ and vendor/fbtransform/ tests in jest Test Plan: jest
2015-03-26 07:48:43 +08:00
"testPathDirs": [
Don't run non-existant fbtransform tests
2015-05-14 01:52:51 +08:00
"<rootDir>/src"
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
}