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

132 lines
4.1 KiB
JSON
Raw Normal View History

Initial public release
2013-05-29 12:46:11 -07:00
{
Move react-tools from root. ReactTools is deprecated, it doesn't belong at the root of the project. We'll remove it after 0.14 but for now this moves it so that it's contained and not intermixed with the rest of the project. The currect behavior of copying src/ into the package is maintained.
2015-06-02 14:13:11 -07:00
"name": "react-build",
"private": true,
16.0.0-alpha.3
2017-02-23 15:36:08 -08:00
"version": "16.0.0-alpha.3",
Initial public release
2013-05-29 12:46:11 -07:00
"devDependencies": {
Bundle DOM renderers into their individual UMD bundles (#7164) * Cut out isomorphic dependencies from the renderers These files reaches into isomorphic files. The ReactElement functions are exposed on the React object anyway so I can just use those instead. I also found some files that are not shared that should be in renderers shared. * Found a few more shared dependencies renderSubtreeIntoContainer is only used by the DOM renderer. It's not an addon. ReactClass isn't needed as a dependency since injection doesn't happen anymore. * Use a shim file to load addons' dependencies on DOM By replacing this intermediate file we can do the lazy loading without needing any lazy requires. This set up works with ES modules. We could also replace the globalShim thing with aliased files instead for consistency. * Bundle DOM renderers into their individual UMD bundles Instead of exposing the entire DOM renderer on the react.js package, I only expose CurrentOwner and ComponentTreeDevtool which are currently the only two modules that share __state__ with the renderers. Then I package each renderer in its own package. That could allow us to drop more server dependencies from the client package. It will also allow us to ship fiber as a separate renderer. Unminified DEV after before react.js 123kb 696kb react-with-addons.js 227kb 774kb react-dom.js 668kb 1kb react-dom-server.js 638kb 1kb Minified PROD after before react.min.js 24kb 154kb react-with-addons.min.js 37kb 166kb react-dom.min.js 149kb 1kb react-dom-server.min.js 144kb 1kb The total size for react.min.js + react-dom.min.js is +19kb larger because of the overlap between them right now. I'd like to see what an optimizing compiler can do to this. Some of that is fbjs stuff. There shouldn't need to be that much overlap so that's something we can hunt. We should keep isomorphic absolutely minimal so there's no reason for other React clones not to use it. There will be less overlap with Fiber. However, another strategy that we could do is package the isomorphic package into each renderer bundle and conditionally initialize it if it hasn't already been initialized. That way you only pay an overlap tax when there are two renderers on the page but not without it. It's also easier to just pull in one package. The downside is the versioning stuff that the separate npm package would solve. That applies to CDNs as well. ReactWithAddons is a bit weird because it is packaged into the isomorphic package but has a bunch of DOM dependencies. So we have to load them lazily since the DOM package gets initialized after.
2016-08-09 12:39:03 -07:00
"aliasify": "^2.0.0",
Add (failing) React ART tests This helps us make sure we don't break React ART in a minor or patch release. The idea is to not change these files when making minor or patch changes. Copied directly from react-art with requires fixed. (I also picked a different haste name just in case.)
2016-05-14 15:30:08 -07:00
"art": "^0.10.1",
Add coveralls.
2015-12-21 14:05:03 -06:00
"async": "^1.5.0",
[docs] Upgrade to work with babel 6, fetch remote babel-browser for now
2016-03-07 10:37:06 -08:00
"babel-cli": "^6.6.5",
Update to Babel 6
2016-02-26 16:49:32 -08:00
"babel-core": "^6.0.0",
Upgrade ESLint and dependencies, fix new lint errors, switch Travis to Yarn (#8309) * Update ESLint to 3.10.2 Also pull in fbjs for extending properly, per @zpao. This also disables consistent-return, which has about 80 failing cases in React currently. If we'd like to turn this back on, we should do it separately and fix all the call sites properly (rather than just adding 'return undefined;' everywhere, which adds no value. Fixes to all existing lint errors plus an update for yarn.lock to follow. * Update yarn.lock after the eslint update. * Fix all new eslint failures Unfortunately I had to add three eslint-disable-next-line instances. All have explanations inline. * Switch Travis to use yarn instead of npm
2016-11-17 22:16:44 +00:00
"babel-eslint": "^7.1.0",
Upgrade Jest to v19 (#9034)
2017-02-22 17:59:18 +01:00
"babel-jest": "^19.0.0",
Update to Babel 6
2016-02-26 16:49:32 -08:00
"babel-plugin-check-es2015-constants": "^6.5.0",
"babel-plugin-syntax-trailing-function-commas": "^6.5.0",
upgraded babel-plugin-transform-class-properties - babel/babel#3589 fixed inferring class name
2016-07-23 14:53:59 -07:00
"babel-plugin-transform-class-properties": "^6.11.5",
Update to Babel 6
2016-02-26 16:49:32 -08:00
"babel-plugin-transform-es2015-arrow-functions": "^6.5.2",
"babel-plugin-transform-es2015-block-scoped-functions": "^6.5.0",
Update to babel-plugin-transform-es2015-block-scoping 6.23 (#9002) Now we won't add closures unnecessarily. I verified that we have no code that throws -- adding some then running `grunt build:modules` correctly throws.
2017-02-14 11:24:01 -08:00
"babel-plugin-transform-es2015-block-scoping": "^6.23.0",
Update to Babel 6
2016-02-26 16:49:32 -08:00
"babel-plugin-transform-es2015-classes": "^6.5.2",
"babel-plugin-transform-es2015-computed-properties": "^6.5.2",
"babel-plugin-transform-es2015-destructuring": "^6.5.0",
"babel-plugin-transform-es2015-for-of": "^6.5.2",
"babel-plugin-transform-es2015-literals": "^6.5.0",
"babel-plugin-transform-es2015-modules-commonjs": "^6.5.2",
"babel-plugin-transform-es2015-object-super": "^6.5.0",
"babel-plugin-transform-es2015-parameters": "^6.5.0",
"babel-plugin-transform-es2015-shorthand-properties": "^6.5.0",
"babel-plugin-transform-es2015-spread": "^6.5.2",
"babel-plugin-transform-es2015-template-literals": "^6.5.2",
"babel-plugin-transform-es3-member-expression-literals": "^6.5.0",
"babel-plugin-transform-es3-property-literals": "^6.5.0",
Add Object Spread Support to Our Babel Config Won't really use this in prod code yet but I have a benchmark that uses it.
2016-03-24 16:26:34 -07:00
"babel-plugin-transform-object-rest-spread": "^6.6.5",
fixed transform-react-jsx-source devDep (#6697)
2016-05-04 02:50:27 -04:00
"babel-plugin-transform-react-jsx-source": "^6.8.0",
Update to Babel 6
2016-02-26 16:49:32 -08:00
"babel-preset-react": "^6.5.0",
Add a gulp script for extracting error codes (#6882)
2016-06-01 11:21:26 -07:00
"babel-traverse": "^6.9.0",
[Fiber] Implement test renderer (#8628) * ReactTestRenderer move current impl to stack dir * ReactTestRenderer on fiber: commence! * ReactTestRenderer: most non-ref/non-public-instance tests are passing * Move ReactTestFiberComponent functions from Renderer to Component file * test renderer: get rid of private root containers and root Maps * TestRenderer: switch impl based on ReactDOMFeatureFlag.useFiber * ReactTestRenderer: inline component creation * ReactTestRenderer: return to pristine original glory (+ Fiber for error order difference) * TestRendererFiber: use a simple class as TestComponentInstances * Add `getPublicInstance` to support TestRenderer `createNodeMock` * Rename files to end. Update for `mountContainer->createContainer` change * test renderer return same object to prevent unnecessary context pushing/popping * Fiber HostConfig add getPublicInstance. This should be the identity fn everywhere except the test renderer * appease flow * Initial cleanup from sleepy work * unstable_batchedUpdates * Stack test renderer: cache nodeMock to not call on unmount * add public instance type parameter to the reconciler * test renderer: set _nodeMock when mounted * More cleanup * Add test cases for root fragments and (maybe?) root text nodes * Fix the npm package build Explicitly require the Stack version by default. Add a separate entry point for Fiber. We don't add fiber.js to the package yet since it's considered internal until React 16. * Relax the ref type from Object to mixed This seems like the most straightforward way to support getPublicInstance for test renderer. * Remove accidental newline * test renderer: unify TestComponent and TestContainer, handle root updates * Remove string/number serialization attempts since Fiber ensures all textInstances are strings * Return full fragments in toJSON * Test Renderer remove TestComponent instances for simple objects * Update babylon for exact object type syntax * Use $$typeof because clarity > punching ducks. * Minor Flow annotation tweaks * Tweak style, types, and naming * Fix typo
2017-01-11 14:19:32 -05:00
"babylon": "6.15.0",
Upgrade browserify
2016-04-05 10:53:53 -07:00
"browserify": "^13.0.0",
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",
devDependencies: add core-js and es6-symbol polyfill for tests
2016-04-02 14:26:35 +02:00
"core-js": "^2.2.1",
Add coveralls.
2015-12-21 14:05:03 -06:00
"coveralls": "^2.11.6",
update deps
2015-11-12 16:02:45 +03:00
"del": "^2.0.2",
update deps
2015-10-27 01:15:00 +03:00
"derequire": "^2.0.3",
Upgrade ESLint and dependencies, fix new lint errors, switch Travis to Yarn (#8309) * Update ESLint to 3.10.2 Also pull in fbjs for extending properly, per @zpao. This also disables consistent-return, which has about 80 failing cases in React currently. If we'd like to turn this back on, we should do it separately and fix all the call sites properly (rather than just adding 'return undefined;' everywhere, which adds no value. Fixes to all existing lint errors plus an update for yarn.lock to follow. * Update yarn.lock after the eslint update. * Fix all new eslint failures Unfortunately I had to add three eslint-disable-next-line instances. All have explanations inline. * Switch Travis to use yarn instead of npm
2016-11-17 22:16:44 +00:00
"eslint": "^3.10.2",
"eslint-config-fbjs": "^1.1.1",
"eslint-plugin-babel": "^3.3.0",
"eslint-plugin-flowtype": "^2.25.0",
"eslint-plugin-react": "^6.7.1",
Rename rule to no-primitive-constructors
2017-02-28 15:59:45 -08:00
"eslint-plugin-react-internal": "file:./eslint-rules",
Bump fbjs to 0.8.9 (#8910)
2017-02-06 19:02:17 +00:00
"fbjs": "^0.8.9",
Upgrade fbjs
2016-04-05 10:50:54 -07:00
"fbjs-scripts": "^0.6.0",
Update Flow to 0.37.0 (#8608) Nothing really changes.
2016-12-20 11:09:03 -08:00
"flow-bin": "^0.37.0",
Add coveralls.
2015-12-21 14:05:03 -06:00
"glob": "^6.0.1",
Add script to print out a list of warnings We'll use this in the GH sync script to track which warnings have changed since the last sync
2017-03-02 11:18:46 -08:00
"glob-stream": "^6.1.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",
Use fbjs package from npm, gulp This reworks a few things in building and distributing React. The biggest change is using fbjs to share dependencies with other libraries. We're also using Gulp for some build steps.
2015-07-17 18:20:38 -07:00
"gulp": "^3.9.0",
Update to Babel 6
2016-02-26 16:49:32 -08:00
"gulp-babel": "^6.0.0",
update deps
2015-10-27 01:15:00 +03:00
"gulp-flatten": "^0.2.0",
Gulp: lint, flow, and version-check (#7174) * Add plugin loading for gulp * Convert `lint` task to gulp * Convert `flow` task to gulp * Convert `version-check` task to gulp * Add missing semicolons
2016-07-05 16:30:09 -04:00
"gulp-load-plugins": "^1.2.4",
Add a gulp script for extracting error codes (#6882)
2016-06-01 11:21:26 -07:00
"gulp-util": "^3.0.7",
Minify both before and after browserify
2013-12-28 23:41:54 -07:00
"gzip-js": "~0.3.2",
Upgrade Jest to v19 (#9034)
2017-02-22 17:59:18 +01:00
"jest": "^19.0.1",
"jest-config": "^19.0.1",
"jest-jasmine2": "^19.0.1",
"jest-runtime": "^19.0.1",
Use loose-envify instead of envify This reduces the number of transitive dependencies and decreases the build time (by ~6% on my machine).
2016-03-19 23:28:50 +01:00
"loose-envify": "^1.1.0",
Build renderers into their individual npm packages (#7168) This copies modules into three separate packages instead of putting it all in React. The overlap in shared and between renderers gets duplicated. This allows the isomorphic package to stay minimal. It can also be used as a direct dependency without much risk. This also allow us to ship versions to each renderer independently and we can ship renderers without updating the main react package dependency.
2016-08-10 18:17:49 -07:00
"merge-stream": "^1.0.0",
Preserve license headers from dependencies in minified build (#8803) * Preserve license headers from dependencies in minified build Fixes #8789. * Bump minimal object-assign version
2017-01-20 02:29:06 +01:00
"object-assign": "^4.1.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",
update deps
2015-10-27 01:15:00 +03:00
"run-sequence": "^1.1.4",
Use fbjs package from npm, gulp This reworks a few things in building and distributing React. The biggest change is using fbjs to share dependencies with other libraries. We're also using Gulp for some build steps.
2015-07-17 18:20:38 -07:00
"through2": "^2.0.0",
update deps
2015-10-27 01:15:00 +03:00
"tmp": "~0.0.28",
update typescript
2016-05-03 02:08:12 +03:00
"typescript": "~1.8.10",
update deps
2015-10-27 01:15:00 +03:00
"uglify-js": "^2.5.0",
Run fiber tests just once on Travis (#8221) Consolidate facts tracking with the other script.
2016-11-07 11:43:29 -08:00
"uglifyify": "^3.0.1",
"yargs": "^6.3.0"
Initial public release
2013-05-29 12:46:11 -07:00
},
Check for compatible node,npm versions on install This is only for building React and doesnn't apply to production installs.
2015-08-18 18:05:13 -07:00
"devEngines": {
Add support for node v7 (#8135)
2016-10-29 13:24:12 +03:00
"node": "4.x || 5.x || 6.x || 7.x",
Add npm v4.0.0 support (#8082)
2016-10-25 01:57:12 +03:00
"npm": "2.x || 3.x || 4.x"
Recommend Node v0.10.0 due to https://github.com/isaacs/npm/issues/2907
2013-06-27 13:09:29 -07:00
},
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",
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",
Upgrade to fbjs, fbjs-scripts @ 0.2
2015-08-31 17:17:30 -07:00
"postinstall": "node node_modules/fbjs-scripts/node/check-dev-engines.js package.json",
[flow] annotate accumulate and accumulateInto Summary: Trying to start adding flow types to files in React. I needed to add a script to package.json in order to run flow, flow-bin is already a dependency. I had to rewrite the implementation a bit. Flow doesn't recognize ``` var currentIsArray = Array.isArray(current); if (currentIsArray) { // not refined } ``` but the following does work ``` if (Array.isArray(current)) { // refined } ``` Test Plan: npm run-script flow npm run-script test accumulate Reviewers: @zpao @spicyj
2016-06-16 17:18:30 +02:00
"test": "jest",
"flow": "flow"
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/",
"/react/build/"
],
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": "",
Update all Jest packages to 17.x (#8327) * Update all Jest packages to 17.x, cache babel-jest transforms * Remove the caching Looking at the other builds it doesn't seem to actually be that necessary. The bottleneck is executors, not build time. * Remove unnecessary package, fix fiber test runner * Regenerate yarn lockfile
2016-11-20 11:10:08 -05:00
"transform": {
Update to Jest 18 (#8621)
2016-12-21 19:28:27 -08:00
".*": "./scripts/jest/preprocessor.js"
Update all Jest packages to 17.x (#8327) * Update all Jest packages to 17.x, cache babel-jest transforms * Remove the caching Looking at the other builds it doesn't seem to actually be that necessary. The bottleneck is executors, not build time. * Remove unnecessary package, fix fiber test runner * Regenerate yarn lockfile
2016-11-20 11:10:08 -05:00
},
Update to jest 15 Jest 15 has just been released and is way more awesome: http://facebook.github.io/jest/blog/2016/09/01/jest-15.html This pull request updates jest from version 12 to 15. Right now there's a fix in jest around Symbol that hasn't been released yet, so this will break CI and cannot be merged it. But once it ships by the end of the day, we'll be good to go :) See comments inline for all the changes I've done.
2016-08-31 13:33:25 -07:00
"setupFiles": [
Update to Jest 18 (#8621)
2016-12-21 19:28:27 -08:00
"./scripts/jest/environment.js"
Update to jest 15 Jest 15 has just been released and is way more awesome: http://facebook.github.io/jest/blog/2016/09/01/jest-15.html This pull request updates jest from version 12 to 15. Right now there's a fix in jest around Symbol that hasn't been released yet, so this will break CI and cannot be merged it. But once it ships by the end of the day, we'll be good to go :) See comments inline for all the changes I've done.
2016-08-31 13:33:25 -07:00
],
Update to Jest 18 (#8621)
2016-12-21 19:28:27 -08:00
"setupTestFrameworkScriptFile": "./scripts/jest/test-framework-setup.js",
Update to jest 15 Jest 15 has just been released and is way more awesome: http://facebook.github.io/jest/blog/2016/09/01/jest-15.html This pull request updates jest from version 12 to 15. Right now there's a fix in jest around Symbol that hasn't been released yet, so this will break CI and cannot be merged it. But once it ships by the end of the day, we'll be good to go :) See comments inline for all the changes I've done.
2016-08-31 13:33:25 -07:00
"testRegex": "/__tests__/",
"moduleFileExtensions": [
Upgrade babel, babel-eslint; remove babel-core dep
2015-07-21 16:59:25 -07:00
"js",
Update to jest 15 Jest 15 has just been released and is way more awesome: http://facebook.github.io/jest/blog/2016/09/01/jest-15.html This pull request updates jest from version 12 to 15. Right now there's a fix in jest around Symbol that hasn't been released yet, so this will break CI and cannot be merged it. But once it ships by the end of the day, we'll be good to go :) See comments inline for all the changes I've done.
2016-08-31 13:33:25 -07:00
"json",
"node",
"coffee",
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
],
Upgrade Jest to v19 (#9034)
2017-02-22 17:59:18 +01:00
"roots": [
Upgrade babel, babel-eslint; remove babel-core dep
2015-07-21 16:59:25 -07:00
"<rootDir>/eslint-rules",
Remove `generateFromMetadata` and `getMetadata` usage.
2015-10-28 23:38:29 -07:00
"<rootDir>/mocks",
Add a gulp script for extracting error codes (#6882)
2016-06-01 11:21:26 -07:00
"<rootDir>/scripts",
Use fbjs package from npm, gulp This reworks a few things in building and distributing React. The biggest change is using fbjs to share dependencies with other libraries. We're also using Gulp for some build steps.
2015-07-17 18:20:38 -07:00
"<rootDir>/src",
"node_modules/fbjs"
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
],
Restore coverage in Travis (#7628) We disabled coverage in Travis because the implementation was crashing ( https://github.com/facebook/react/issues/6290 ). Since we upgraded to Jest 15, the entire coverage implementation is brand new so we should give it another try.
2016-09-02 14:23:58 -07:00
"collectCoverageFrom": [
"src/**/*.js",
Move webcomponents.js polyfill to mocks (#8993) * Move webcomponents.js polyfill to mocks I'd like to move it out of shared to make it easier to sync this to RN. Since this is only used for testing and a polyfill is essentially a mock. Maybe this makes sense? Rename to camel case to be consistent with providesModule. * Update path to ignore in configs
2017-02-27 18:35:05 -08:00
"!src/__mocks__/vendor/third_party/*.js",
Restore coverage in Travis (#7628) We disabled coverage in Travis because the implementation was crashing ( https://github.com/facebook/react/issues/6290 ). Since we upgraded to Jest 15, the entire coverage implementation is brand new so we should give it another try.
2016-09-02 14:23:58 -07:00
"!src/test/*.js"
],
Update to jest 15 Jest 15 has just been released and is way more awesome: http://facebook.github.io/jest/blog/2016/09/01/jest-15.html This pull request updates jest from version 12 to 15. Right now there's a fix in jest around Symbol that hasn't been released yet, so this will break CI and cannot be merged it. But once it ships by the end of the day, we'll be good to go :) See comments inline for all the changes I've done.
2016-08-31 13:33:25 -07:00
"timers": "fake"
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