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

60 lines
1.3 KiB
JSON
Raw Normal View History

Initial public release
2013-05-30 03:46:11 +08:00
{
"name": "react-tools",
Bump to 0.3.1
2013-05-31 03:14:43 +08:00
"version": "0.3.1",
Initial public release
2013-05-30 03:46:11 +08:00
"keywords": [
"clientside"
],
"homepage": "https://facebook.github.io/react",
"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/",
Initial public release
2013-05-30 03:46:11 +08:00
"vendor/fbtransform/",
"vendor/woodchipper.js"
],
"main": "main.js",
"bin": {
"jsx": "./bin/jsx"
},
"repository": {
"type": "git",
"url": "https://github.com/facebook/react"
},
"scripts": {
"test": "grunt test"
},
"dependencies": {
"base62": "~0.1.1",
"commoner": "~0.6.8",
"esprima": "git://github.com/facebook/esprima#fb-harmony",
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
"recast": "~0.3.3",
"source-map": "~0.1.22"
Initial public release
2013-05-30 03:46:11 +08:00
},
"devDependencies": {
"browserify": "~2.14.2",
"wrapup": "~0.12.0",
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",
"grunt-contrib-jshint": "~0.5.4",
"optimist": "~0.4.0",
"phantomjs": ">= 1.9.0",
"semver": ">= 1.1.4",
"uglify-js": "~2.3.6",
"grunt-contrib-clean": "~0.4.1",
"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"
},
"preferGlobal": true
}