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

98 lines
2.3 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 to beta1
2015-07-03 10:28:21 +02:00
"version": "0.14.0-beta1",
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
"jsx",
Upgrade babel, babel-eslint; remove babel-core dep
2015-07-21 16:59:25 -07:00
"react",
v0.3.2 Also some tweaks to package.json details.
2013-05-31 16:52:38 -07:00
"transformer",
"view"
Initial public release
2013-05-29 12:46:11 -07: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-18 15:41:56 -07:00
"homepage": "https://facebook.github.io/react",
Initial public release
2013-05-29 12:46:11 -07:00
"bugs": "https://github.com/facebook/react/issues",
BSD + PATENTS
2014-10-08 17:27:59 -07:00
"license": "BSD-3-Clause",
Initial public release
2013-05-29 12:46:11 -07:00
"files": [
"bin/jsx",
Upgrade babel, babel-eslint; remove babel-core dep
2015-07-21 16:59:25 -07:00
"main.js",
Remove transforms from repo, react-tools Time to just use jstransform.
2015-04-28 15:14:42 -07:00
"src/"
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",
Remove transforms from repo, react-tools Time to just use jstransform.
2015-04-28 15:14:42 -07:00
"jstransform": "^11.0.0"
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",
"babel-eslint": "^3.1.25",
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",
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",
Upgrade eslint Fixes #4428.
2015-07-20 08:37:47 -07:00
"eslint": "^0.24.1",
Enable react/wrap-multilines eslint rule Multiline jsx literals in a return should be paren-wrapped.
2015-06-02 10:43:42 -07: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-04 17:04:45 -07: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-03 15:09:50 -07:00
"eslint-tester": "^0.7.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",
More conservative dependency update.
2015-06-26 18:37:15 -07:00
"grunt-jest": "^0.1.3",
Minify both before and after browserify
2013-12-28 23:41:54 -07:00
"gzip-js": "~0.3.2",
More conservative dependency update.
2015-06-26 18:37:15 -07:00
"jest-cli": "^0.4.13",
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",
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",
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-01 22:41:00 -08: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
},
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": {
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",
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-04 16:21:43 -08:00
"jest": "jest",
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",
"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/",
"/node_modules/",
"/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": "",
"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 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",
"<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-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