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

40 lines
815 B
JSON
Raw Normal View History

ReactTestRenderer package (#7362)
2016-07-29 12:39:05 +08:00
{
"name": "react-test-renderer",
Fixed invalid DevTools work tags (#20362) * Fixed invalid DevTools work tags Work tags changed recently (PR #13902) but we didn't bump React versions. This meant that DevTools has valid work tags only for master (and FB www sync) but invalid work tags for the latest open source releases. To fix this, I incremneted React's version in Git (without an actual release) and added a new fork to the work tags detection branch. This commit also adds tags for the experimental Scope and Fundamental APIs to DevTools so component names will at least display correctly. Technically these new APIs were first introduced to experimental builds ~16.9 but I didn't add a new branch to the work tags fork because I don't they're used commonly. I've just added them to the 17+ branches. * Removed FundamentalComponent from DevTools tag defs
2020-12-01 23:33:32 +08:00
"version": "17.0.2",
ReactTestRenderer package (#7362)
2016-07-29 12:39:05 +08:00
"description": "React package for snapshot testing.",
"main": "index.js",
Add directory details to the package.json of all packages (#14628) Specifying the directory as part of the `repository` field in a `package.json` allows third party tools to provide better support when working with monorepos. For example, it allows them to correctly construct a commit diff for a specific package. This format was accepted by npm in https://github.com/npm/rfcs/pull/19.
2019-01-19 04:21:12 +08:00
"repository": {
16.8.0
2019-02-06 16:04:00 +08:00
"type": "git",
"url": "https://github.com/facebook/react.git",
Add directory details to the package.json of all packages (#14628) Specifying the directory as part of the `repository` field in a `package.json` allows third party tools to provide better support when working with monorepos. For example, it allows them to correctly construct a commit diff for a specific package. This format was accepted by npm in https://github.com/npm/rfcs/pull/19.
2019-01-19 04:21:12 +08:00
"directory": "packages/react-test-renderer"
},
Updating package versions for release 16.3.0-alpha.3
2018-03-23 03:41:43 +08:00
"keywords": [
"react",
"react-native",
"react-testing"
],
Change license and remove references to PATENTS Only remaining references: ``` docs/_posts/2014-10-28-react-v0.12.md 51:You can read the full text of the [LICENSE](https://github.com/facebook/react/blob/master/LICENSE) and [`PATENTS`](https://github.com/facebook/react/blob/master/PATENTS) files on GitHub. docs/_posts/2015-04-17-react-native-v0.4.md 20:* **Patent Grant**: Many of you had concerns and questions around the PATENTS file. We pushed [a new version of the grant](https://code.facebook.com/posts/1639473982937255/updating-our-open-source-patent-grant/). src/__mocks__/vendor/third_party/WebComponents.js 8: * subject to an additional IP rights grant found at http://polymer.github.io/PATENTS.txt ```
2017-09-25 04:49:31 +08:00
"license": "MIT",
ReactTestRenderer package (#7362)
2016-07-29 12:39:05 +08:00
"bugs": {
"url": "https://github.com/facebook/react/issues"
},
[Gatsby] "https://facebook.github.io/react/" -> "https://reactjs.org/" (#10970)
2017-09-30 09:43:22 +08:00
"homepage": "https://reactjs.org/",
add dependencies to react-test-renderer and react-addons (#8467) **What** and **Why**: * When using npm version 2, `object-assign` and `fbjs` were not getting properly installed * This PR adds `object-assign` and `fbjs` as explicit dependencies to both `react-test-renderer` and `react-addons`
2016-12-02 00:37:14 +08:00
"dependencies": {
Add "prop-types" to dependencies of "react-test-renderer" (#11340)
2017-10-23 23:14:33 +08:00
"object-assign": "^4.1.1",
Fixed invalid DevTools work tags (#20362) * Fixed invalid DevTools work tags Work tags changed recently (PR #13902) but we didn't bump React versions. This meant that DevTools has valid work tags only for master (and FB www sync) but invalid work tags for the latest open source releases. To fix this, I incremneted React's version in Git (without an actual release) and added a new fork to the work tags detection branch. This commit also adds tags for the experimental Scope and Fundamental APIs to DevTools so component names will at least display correctly. Technically these new APIs were first introduced to experimental builds ~16.9 but I didn't add a new branch to the work tags fork because I don't they're used commonly. I've just added them to the 17+ branches. * Removed FundamentalComponent from DevTools tag defs
2020-12-01 23:33:32 +08:00
"react-is": "^17.0.2",
Revert accidental changes to package.json (#18348) The publish script was written before we switched to running patch releases out-of-band, so when updating the local package.json version numbers, it accidentally reverted other changes that have landed to master since 16.13 was released.
2020-03-20 04:16:37 +08:00
"react-shallow-renderer": "^16.13.1",
17.0.1
2020-10-22 20:24:46 +08:00
"scheduler": "^0.20.1"
add dependencies to react-test-renderer and react-addons (#8467) **What** and **Why**: * When using npm version 2, `object-assign` and `fbjs` were not getting properly installed * This PR adds `object-assign` and `fbjs` as explicit dependencies to both `react-test-renderer` and `react-addons`
2016-12-02 00:37:14 +08:00
},
ReactTestRenderer package (#7362)
2016-07-29 12:39:05 +08:00
"peerDependencies": {
Fixed invalid DevTools work tags (#20362) * Fixed invalid DevTools work tags Work tags changed recently (PR #13902) but we didn't bump React versions. This meant that DevTools has valid work tags only for master (and FB www sync) but invalid work tags for the latest open source releases. To fix this, I incremneted React's version in Git (without an actual release) and added a new fork to the work tags detection branch. This commit also adds tags for the experimental Scope and Fundamental APIs to DevTools so component names will at least display correctly. Technically these new APIs were first introduced to experimental builds ~16.9 but I didn't add a new branch to the work tags fork because I don't they're used commonly. I've just added them to the 17+ branches. * Removed FundamentalComponent from DevTools tag defs
2020-12-01 23:33:32 +08:00
"react": "17.0.2"
Fix Suspense-wrapping heuristic (and bump version numbers) (#19373) * Fixed suspense wrapping heuristic * Bump package numbers 16.13.1 -> 17.0.0-alpha.0 to fix DevTools Suspense heuristic
2020-07-16 00:25:27 +08:00
},
Updating package versions for release 16.3.0-alpha.3
2018-03-23 03:41:43 +08:00
"files": [
"LICENSE",
"README.md",
Publish a local release (canary or stable) to NPM (#14260) New release scripts. Learn more at https://github.com/facebook/react/blob/master/scripts/release/README.md
2018-11-24 04:37:18 +08:00
"build-info.json",
Updating package versions for release 16.3.0-alpha.3
2018-03-23 03:41:43 +08:00
"index.js",
"shallow.js",
Added UMD build to test renderer package (#12594)
2018-04-10 22:49:19 +08:00
"cjs/",
"umd/"
Updating package versions for release 16.3.0-alpha.3
2018-03-23 03:41:43 +08:00
]
ReactTestRenderer package (#7362)
2016-07-29 12:39:05 +08:00
}