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

67 lines
1.4 KiB
JSON
Raw Normal View History

Initial public release
2013-05-30 03:46:11 +08:00
{
"name": "react-tools",
Version bump for 0.5.0 development
2013-07-18 07:45:38 +08:00
"version": "0.5.0-alpha",
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",
"licenses": [
{
"type": "Apache-2.0",
"url": "http://www.apache.org/licenses/LICENSE-2.0"
}
],
"files": [
"README.md",
"main.js",
"bin/jsx",
Ship CJS modules instead of browserified build It turns out that if you try to browserify a file requiring react-tools, it doesn't work. This is because browserify just visits the require statements in the file and looks for files in that path. ./ReactCompositeComponent doesn't exist and that's the point that fails. So the fix is to actually ship each of our CJS modules as individual files like browserify expects. This should have no negative side effects - we still only export React (though the rest of our modules are now actually accessible, which might make it easier to do more with the module). The other change here is to move source-map to dependencies since it's required in the transform code. Test Plan: ``` $ npm pack . $ cd /tmp $ npm install path/to/react-tools-0.3.1.tgz $ echo "require('react-tools')" > test.js $ browserify test.js ```
2013-06-01 01:57:40 +08:00
"build/modules/",
[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/",
Initial public release
2013-05-30 03:46:11 +08:00
"vendor/fbtransform/",
Fix package.json's reference to vendor/constants.js
2013-06-18 07:27:07 +08:00
"vendor/constants.js"
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"
},
"scripts": {
Run `grunt build` with `npm test` so that we can upload all files
2013-07-23 09:16:44 +08:00
"test": "grunt build && grunt test"
Initial public release
2013-05-30 03:46:11 +08:00
},
"dependencies": {
Upgrade Commoner and Populist to force upgrade to graceful-fs v2.0.0. A silent upgrade from graceful-fs v1.2.2 to v1.2.3 (a dependency for both Commoner and Populist) broke the build process, even though tests were still passing. The 2.0.0 version fixes whatever was broken, though I won't pretend to know exactly what the root cause was.
2013-07-17 03:42:17 +08:00
"commoner": "~0.8.4",
Move to using `jstransform` and `esprima-fb` npm modules
2013-08-20 05:37:25 +08:00
"esprima-fb": "1001.1001.1000-dev-harmony-fb",
Simplify bin/jsx to perform just the JSX transform. We will continue using `bin/jsx-internal`, well, internally. Note that this version no longer respects `@providesModule`, and it doesn't do anything special with constants like `__DEV__`, so we can no longer get to claim that `bin/jsx` can be used to build the core. I'm happy about this, personally, because it demonstrates the flexibility of Commoner.
2013-09-07 04:09:30 +08:00
"jstransform": "~1.0.0"
Initial public release
2013-05-30 03:46:11 +08:00
},
"devDependencies": {
Update package dependencies Sometimes I look at https://david-dm.org/facebook/react
2013-08-28 05:46:06 +08:00
"browserify": "~2.29.0",
Initial public release
2013-05-30 03:46:11 +08:00
"wrapup": "~0.12.0",
Upgrade Commoner and Populist to force upgrade to graceful-fs v2.0.0. A silent upgrade from graceful-fs v1.2.2 to v1.2.3 (a dependency for both Commoner and Populist) broke the build process, even though tests were still passing. The 2.0.0 version fixes whatever was broken, though I won't pretend to know exactly what the root cause was.
2013-07-17 03:42:17 +08:00
"populist": "~0.1.3",
Add `grunt-cli` to devDependencies to make sure it's installed for travisci
2013-05-30 07:17:49 +08:00
"grunt-cli": "~0.1.9",
Initial public release
2013-05-30 03:46:11 +08:00
"grunt": "~0.4.1",
"grunt-contrib-copy": "~0.4.1",
Upgrade other dependencies Nothing groundbreaking. `semver` was likely already installed at 2.0.x anyway (since >=) and `grunt-contrib-jshint` just gives us `jshint` @ 2.1.3
2013-07-10 01:55:56 +08:00
"grunt-contrib-jshint": "~0.6.0",
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",
Upgrade phantomjs to 1.9.1-4 This fixes the install and permissions issues we've been seeing with other 1.9.1-x versions.
2013-08-14 06:35:52 +08:00
"phantomjs": "~1.9.1-4",
Make constant propagation smarter about pruning if statements.
2013-09-12 05:56:42 +08:00
"recast": "~0.4.16",
Update package dependencies Sometimes I look at https://david-dm.org/facebook/react
2013-08-28 05:46:06 +08:00
"semver": "~2.1.0",
"uglify-js": "~2.4.0",
"grunt-contrib-clean": "~0.5.0",
Initial public release
2013-05-30 03:46:11 +08:00
"grunt-compare-size": "~0.4.0",
"gzip-js": "~0.3.2",
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",
Initial public release
2013-05-30 03:46:11 +08:00
"grunt-contrib-compress": "~0.5.1"
},
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"
},
Initial public release
2013-05-30 03:46:11 +08:00
"preferGlobal": true
}