MORPH
SIGN IN SIGN UP
facebook / react UNCLAIMED

The library for web and native user interfaces.

244237 0 31 JavaScript
Normal View History Raw
Build react-dom package
2015-06-11 14:19:52 -07:00
{
"name": "react-dom",
Bump next prerelease version numbers (#34674)
2025-10-02 00:31:55 +02:00
"version": "19.3.0",
Build react-dom package
2015-06-11 14:19:52 -07:00
"description": "React package for working with the DOM.",
"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-18 20:21:12 +00:00
"repository": {
16.8.0
2019-02-06 08:04:00 +00: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-18 20:21:12 +00:00
"directory": "packages/react-dom"
},
Build react-dom package
2015-06-11 14:19:52 -07:00
"keywords": [
"react"
],
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-24 13:49:31 -07:00
"license": "MIT",
Build react-dom package
2015-06-11 14:19:52 -07:00
"bugs": {
"url": "https://github.com/facebook/react/issues"
},
Update homepage URLs to react.dev (#28478) Updates the package.json "homepage" entry to react.dev
2024-03-01 14:35:18 -05:00
"homepage": "https://react.dev/",
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
"dependencies": {
Bump next prerelease version numbers (#34674)
2025-10-02 00:31:55 +02:00
"scheduler": "^0.28.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
},
Make React a peerDep of react-dom
2015-11-02 10:19:04 -08:00
"peerDependencies": {
Bump next prerelease version numbers (#34674)
2025-10-02 00:31:55 +02:00
"react": "^19.3.0"
Specify "files" field for npm packages (#7396)
2016-08-02 15:11:45 -07:00
},
"files": [
"LICENSE",
"README.md",
Move createRoot/hydrateRoot to react-dom/client (#23385) * Move createRoot/hydrateRoot to /client We want these APIs ideally to be imported separately from things you might use in arbitrary components (like flushSync). Those other methods are "isomorphic" to how the ReactDOM tree is rendered. Similar to hooks. E.g. importing flushSync into a component that only uses it on the client should ideally not also pull in the entry client implementation on the server. This also creates a nicer parity with /server where the roots are in a separate entry point. Unfortunately, I can't quite do this yet because we have some legacy APIs that we plan on removing (like findDOMNode) and we also haven't implemented flushSync using a flag like startTransition does yet. Another problem is that we currently encourage these APIs to be aliased by /profiling (or unstable_testing). In the future you don't have to alias them because you can just change your roots to just import those APIs and they'll still work with the isomorphic forms. Although we might also just use export conditions for them. For that all to work, I went with a different strategy for now where the real API is in / but it comes with a warning if you use it. If you instead import /client it disables the warning in a wrapper. That means that if you alias / then import /client that will inturn import the alias and it'll just work. In a future breaking changes (likely when we switch to ESM) we can just remove createRoot/hydrateRoot from / and move away from the aliasing strategy. * Update tests to import from react-dom/client * Fix fixtures * Update warnings * Add test for the warning * Update devtools * Change order of react-dom, react-dom/client alias I think the order matters here. The first one takes precedence. * Require react-dom through client so it can be aliased Co-authored-by: Andrew Clark <git@andrewclark.io>
2022-03-01 00:13:28 -05:00
"client.js",
[DOM] Fix package.json files for #28784 (#28785) Missed some files for the react-server disallow client change in #28784
2024-04-08 15:49:18 -07:00
"client.react-server.js",
"index.js",
Added react-dom/profiling entry point to NPM package (#13570)
2018-09-05 11:16:43 -07:00
"profiling.js",
[DOM] Fix package.json files for #28784 (#28785) Missed some files for the react-server disallow client change in #28784
2024-04-08 15:49:18 -07:00
"profiling.react-server.js",
"react-dom.react-server.js",
Use single entry point for SSR via browser field (#10362) * Use single entry point for SSR via browser field * Add server.browser entry point and smoke tests * Tweak bundle naming * Fix import * Re-record * Fix the robot nits * Add resetModules for some extra isolation
2017-08-03 00:41:09 +01:00
"server.browser.js",
[DOM] Fix package.json files for #28784 (#28785) Missed some files for the react-server disallow client change in #28784
2024-04-08 15:49:18 -07:00
"server.bun.js",
Add Edge Server Builds for workerd / edge-light (#26116) We currently abuse the browser builds for Web streams derived environments. We already have a special build for Bun but we should also have one for [other "edge" runtimes](https://runtime-keys.proposal.wintercg.org/) so that we can maximally take advantage of the APIs that exist on each platform. In practice, we currently check for a global property called `AsyncLocalStorage` in the server browser builds which we shouldn't really do since browsers likely won't ever have it. Additionally, this should probably move to an import which we can't add to actual browser builds where that will be an invalid import. So it has to be a separate build. That's not done yet in this PR but Vercel will follow Cloudflare's lead here. The `deno` key still points to the browser build since there's no AsyncLocalStorage there but it could use this same or a custom build if support is added.
2023-02-07 15:10:01 -05:00
"server.edge.js",
[DOM] Fix package.json files for #28784 (#28785) Missed some files for the react-server disallow client change in #28784
2024-04-08 15:49:18 -07:00
"server.js",
Drop Haste (#11303) * Use relative paths in packages/react * Use relative paths in packages/react-art * Use relative paths in packages/react-cs * Use relative paths in other packages * Fix as many issues as I can This uncovered an interesting problem where ./b from package/src/a would resolve to a different instantiation of package/src/b in Jest. Either this is a showstopper or we can solve it by completely fobbidding remaining /src/. * Fix all tests It seems we can't use relative requires in tests anymore. Otherwise Jest becomes confused between real file and symlink. https://github.com/facebook/jest/issues/3830 This seems bad... Except that we already *don't* want people to create tests that import individual source files. All existing cases of us doing so are actually TODOs waiting to be fixed. So perhaps this requirement isn't too bad because it makes bad code looks bad. Of course, if we go with this, we'll have to lint against relative requires in tests. It also makes moving things more painful. * Prettier * Remove @providesModule * Fix remaining Haste imports I missed earlier * Fix up paths to reflect new flat structure * Fix Flow * Fix CJS and UMD builds * Fix FB bundles * Fix RN bundles * Prettier * Fix lint * Fix warning printing and error codes * Fix buggy return * Fix lint and Flow * Use Yarn on CI * Unbreak Jest * Fix lint * Fix aliased originals getting included in DEV Shouldn't affect correctness (they were ignored) but fixes DEV size regression. * Record sizes * Fix weird version in package.json * Tweak bundle labels * Get rid of output option by introducing react-dom/server.node * Reconciler should depend on prop-types * Update sizes last time
2017-10-25 02:55:00 +03:00
"server.node.js",
[DOM] Fix package.json files for #28784 (#28785) Missed some files for the react-server disallow client change in #28784
2024-04-08 15:49:18 -07:00
"server.react-server.js",
Add entry points for "static" server rendering passes (#24752) This will be used to add optimizations for static server rendering.
2022-06-18 22:34:31 -04:00
"static.browser.js",
Add Edge Server Builds for workerd / edge-light (#26116) We currently abuse the browser builds for Web streams derived environments. We already have a special build for Bun but we should also have one for [other "edge" runtimes](https://runtime-keys.proposal.wintercg.org/) so that we can maximally take advantage of the APIs that exist on each platform. In practice, we currently check for a global property called `AsyncLocalStorage` in the server browser builds which we shouldn't really do since browsers likely won't ever have it. Additionally, this should probably move to an import which we can't add to actual browser builds where that will be an invalid import. So it has to be a separate build. That's not done yet in this PR but Vercel will follow Cloudflare's lead here. The `deno` key still points to the browser build since there's no AsyncLocalStorage there but it could use this same or a custom build if support is added.
2023-02-07 15:10:01 -05:00
"static.edge.js",
[DOM] Fix package.json files for #28784 (#28785) Missed some files for the react-server disallow client change in #28784
2024-04-08 15:49:18 -07:00
"static.js",
Add entry points for "static" server rendering passes (#24752) This will be used to add optimizations for static server rendering.
2022-06-18 22:34:31 -04:00
"static.node.js",
[DOM] Fix package.json files for #28784 (#28785) Missed some files for the react-server disallow client change in #28784
2024-04-08 15:49:18 -07:00
"static.react-server.js",
Shallow renderer and test utils bundles (#9426) Shallow renderer and test utils bundles Adds new bundles introduced with React 15.5 release to master (and 16 alpha) react-dom/test-utils: This new bundle contains what used to be react-addons-test-utils. This bundle shares things from react-dom rather than duplicates them. A temporary createRenderer method has been left behind as a way to access the new shallow renderer. This is for the ReactNative release cycle only and should be going away before the final release. react-test-renderer/shallow: This new shallow renderer is almost entirely stand-alone (in that it doesn't use the React reconciler or scheduler). The only touch points are ReactElement and prop/context validation. This renderer is stack and fiber compatible.
2017-04-19 16:45:31 -07:00
"test-utils.js",
Add test selectors to experimental build (#22760) This change adds a new "react-dom/unstable_testing" entry point but I believe its contents will exactly match "react-dom/index" for the stable build. (The experimental build will have the added new selector APIs.)
2021-11-16 16:27:10 -05:00
"unstable_testing.js",
[DOM] Fix package.json files for #28784 (#28785) Missed some files for the react-server disallow client change in #28784
2024-04-08 15:49:18 -07:00
"unstable_testing.react-server.js",
Scaffolding for react-dom/unstable_external-server-runtime (#25482) * Scaffolding for react-dom/unstable_external-server-runtime Implements a new bundle type for in our build config called BROWSER_SCRIPT. This is intended for scripts that get delivered straight to the browser without needing to be processed by a bundler. (And also doesn't include any extra UMD crap.) Right now there's only a single use case so I didn't stress about making it general purpose. The use case is: a script that loads the Fizz browser runtime, and sets up a MutationObserver to receive instructions as HTML streams in. This will be an alternative option to the default Fizz behavior of sending the runtime down as inline script tags, to accommodate environments where inline script tags are not allowed. There's no development version of this bundle because it doesn't contain any warnings or run any user code. None of the actual implementation is in this PR; it just sets up the build infra. Co-authored-by: Mofei Zhang <feifei0@fb.com> * Set BUNDLE_SCRIPT's GCC output format to ES5 This removes the automatic 'use strict' directive, which we don't need. Co-authored-by: Mofei Zhang <feifei0@fb.com>
2022-10-14 23:29:17 -04:00
"unstable_server-external-runtime.js",
[UMD] Remove umd builds (#28735) In React 19 React will finally stop publishing UMD builds. This is motivated primarily by the lack of use of UMD format and the added complexity of maintaining build infra for these releases. Additionally with ESM becoming more prevalent in browsers and services like esm.sh which can host React as an ESM module there are other options for doing script tag based react loading. This PR removes all the UMD build configs and forks. There are some fixtures that still have references to UMD builds however many of them already do not work (for instance they are using legacy features like ReactDOM.render) and rather than block the removal on these fixtures being brought up to date we'll just move forward and fix or removes fixtures as necessary in the future.
2024-04-17 11:15:27 -07:00
"cjs/"
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
],
Add exports field to react-dom (#23252) This configures the exports field for react-dom. Notably there are some conditions for the /server entry point where we pick the export based on environments. Most environments now support Web Streams which is preferred in those environments. We already do this using the "browser" field so the "browser" condition applies here too. I don't think it's necessary, but I also specified "worker" explicitly since this is for Service Workers and those are often targeted with Web Pack's "webworker" target, which is also what Cloudflare currently recommends. I also added "deno" but deno is a bit special because this only works if you run with the node compatibility since otherwise you have to specify absolute URLs for the imports.
2022-02-08 17:19:52 -05:00
"exports": {
Restrict React DOM imports from Server Components (#27382) Adds a separate entry point for the react-dom package when it's accessed from a Server Component environment, using the "react-server" export condition. When you're inside a Server Component module, you won't be able to import client-only APIs like useState. This applies to almost all React DOM exports, except for Float ones like preload.
2023-09-15 14:53:19 -04:00
".": {
Rename "shared subset" to "server" (#27939) The internal file ReactSharedSubset is what the `react` module resolves to when imported from a Server Component environment. We gave it this name because, originally, the idea was that Server Components can access a subset of the APIs available on the client. However, since then, we've also added APIs that can _only_ by accessed on the server and not the client. In other words, it's no longer a subset, it's a slightly different overlapping set. So this commit renames ReactSharedSubet to ReactServer and updates all the references. This does not affect the public API, only our internal implementation.
2024-01-16 19:58:11 -05:00
"react-server": "./react-dom.react-server.js",
Restrict React DOM imports from Server Components (#27382) Adds a separate entry point for the react-dom package when it's accessed from a Server Component environment, using the "react-server" export condition. When you're inside a Server Component module, you won't be able to import client-only APIs like useState. This applies to almost all React DOM exports, except for Float ones like preload.
2023-09-15 14:53:19 -04:00
"default": "./index.js"
},
[DOM] disallow client entrypoints with react-server condition (#28784) `react-server` precludes loading code that expects to be run in a client context. This includes react-dom/client react-dom/server react-dom/unstable_testing react-dom/profiling and react-dom/static This update makes importing any of these client only entrypoints an error
2024-04-08 15:37:06 -07:00
"./client": {
"react-server": "./client.react-server.js",
"default": "./client.js"
},
Add exports field to react-dom (#23252) This configures the exports field for react-dom. Notably there are some conditions for the /server entry point where we pick the export based on environments. Most environments now support Web Streams which is preferred in those environments. We already do this using the "browser" field so the "browser" condition applies here too. I don't think it's necessary, but I also specified "worker" explicitly since this is for Service Workers and those are often targeted with Web Pack's "webworker" target, which is also what Cloudflare currently recommends. I also added "deno" but deno is a bit special because this only works if you run with the node compatibility since otherwise you have to specify absolute URLs for the imports.
2022-02-08 17:19:52 -05:00
"./server": {
[DOM] disallow client entrypoints with react-server condition (#28784) `react-server` precludes loading code that expects to be run in a client context. This includes react-dom/client react-dom/server react-dom/unstable_testing react-dom/profiling and react-dom/static This update makes importing any of these client only entrypoints an error
2024-04-08 15:37:06 -07:00
"react-server": "./server.react-server.js",
Add Edge Server Builds for workerd / edge-light (#26116) We currently abuse the browser builds for Web streams derived environments. We already have a special build for Bun but we should also have one for [other "edge" runtimes](https://runtime-keys.proposal.wintercg.org/) so that we can maximally take advantage of the APIs that exist on each platform. In practice, we currently check for a global property called `AsyncLocalStorage` in the server browser builds which we shouldn't really do since browsers likely won't ever have it. Additionally, this should probably move to an import which we can't add to actual browser builds where that will be an invalid import. So it has to be a separate build. That's not done yet in this PR but Vercel will follow Cloudflare's lead here. The `deno` key still points to the browser build since there's no AsyncLocalStorage there but it could use this same or a custom build if support is added.
2023-02-07 15:10:01 -05:00
"workerd": "./server.edge.js",
Add Bun streaming server renderer (#25597) Add support for Bun server renderer
2022-11-17 13:15:56 -08:00
"bun": "./server.bun.js",
[react-dom/server] Fix hanging on Deno (#35235)
2025-12-04 02:50:27 -03:00
"deno": "./server.node.js",
Add exports field to react-dom (#23252) This configures the exports field for react-dom. Notably there are some conditions for the /server entry point where we pick the export based on environments. Most environments now support Web Streams which is preferred in those environments. We already do this using the "browser" field so the "browser" condition applies here too. I don't think it's necessary, but I also specified "worker" explicitly since this is for Service Workers and those are often targeted with Web Pack's "webworker" target, which is also what Cloudflare currently recommends. I also added "deno" but deno is a bit special because this only works if you run with the node compatibility since otherwise you have to specify absolute URLs for the imports.
2022-02-08 17:19:52 -05:00
"worker": "./server.browser.js",
When selecting a package variant from an export map we should favor n… (#27030) When selecting a package variant from an export map we should favor node over edge-light edge-light represents a runtime with some minimal set of web apis generally found across edge runtimes. However some environments might be both edge-light compatible and node compatible and (node is adding many web APIs) and when both conditions exist we want to favor the node implementations. A followup to this change will add the web streams APIs to Flight and Fizz so the node version exports the same interfaces for web streams that edge does in addition to the node specific implementations.
2023-07-06 10:50:59 -07:00
"node": "./server.node.js",
"edge-light": "./server.edge.js",
Standardize condition order so that edge-lite preferred over browser (#29877) The export maps for react packages have to choose an order of preference. Many runtimes use multiple conditions, for instance when building for edge webpack also uses the browser condition which makes sense given most edge runtimes have a web-standards based set of APIs. However React is building the browser builds primarily for actual browsers and sometimes have builds intended for servers that might be browser compat. This change updates the order of conditions to preference specific named runtimes > node > generic edge runtimes > browser > default
2024-06-12 15:31:23 -07:00
"browser": "./server.browser.js",
Add exports field to react-dom (#23252) This configures the exports field for react-dom. Notably there are some conditions for the /server entry point where we pick the export based on environments. Most environments now support Web Streams which is preferred in those environments. We already do this using the "browser" field so the "browser" condition applies here too. I don't think it's necessary, but I also specified "worker" explicitly since this is for Service Workers and those are often targeted with Web Pack's "webworker" target, which is also what Cloudflare currently recommends. I also added "deno" but deno is a bit special because this only works if you run with the node compatibility since otherwise you have to specify absolute URLs for the imports.
2022-02-08 17:19:52 -05:00
"default": "./server.node.js"
},
[DOM] disallow client entrypoints with react-server condition (#28784) `react-server` precludes loading code that expects to be run in a client context. This includes react-dom/client react-dom/server react-dom/unstable_testing react-dom/profiling and react-dom/static This update makes importing any of these client only entrypoints an error
2024-04-08 15:37:06 -07:00
"./server.browser": {
"react-server": "./server.react-server.js",
"default": "./server.browser.js"
},
"./server.bun": {
"react-server": "./server.react-server.js",
"default": "./server.bun.js"
},
"./server.edge": {
"react-server": "./server.react-server.js",
"default": "./server.edge.js"
},
"./server.node": {
"react-server": "./server.react-server.js",
"default": "./server.node.js"
},
Add entry points for "static" server rendering passes (#24752) This will be used to add optimizations for static server rendering.
2022-06-18 22:34:31 -04:00
"./static": {
[DOM] disallow client entrypoints with react-server condition (#28784) `react-server` precludes loading code that expects to be run in a client context. This includes react-dom/client react-dom/server react-dom/unstable_testing react-dom/profiling and react-dom/static This update makes importing any of these client only entrypoints an error
2024-04-08 15:37:06 -07:00
"react-server": "./static.react-server.js",
Add Edge Server Builds for workerd / edge-light (#26116) We currently abuse the browser builds for Web streams derived environments. We already have a special build for Bun but we should also have one for [other "edge" runtimes](https://runtime-keys.proposal.wintercg.org/) so that we can maximally take advantage of the APIs that exist on each platform. In practice, we currently check for a global property called `AsyncLocalStorage` in the server browser builds which we shouldn't really do since browsers likely won't ever have it. Additionally, this should probably move to an import which we can't add to actual browser builds where that will be an invalid import. So it has to be a separate build. That's not done yet in this PR but Vercel will follow Cloudflare's lead here. The `deno` key still points to the browser build since there's no AsyncLocalStorage there but it could use this same or a custom build if support is added.
2023-02-07 15:10:01 -05:00
"workerd": "./static.edge.js",
Add entry points for "static" server rendering passes (#24752) This will be used to add optimizations for static server rendering.
2022-06-18 22:34:31 -04:00
"deno": "./static.browser.js",
"worker": "./static.browser.js",
When selecting a package variant from an export map we should favor n… (#27030) When selecting a package variant from an export map we should favor node over edge-light edge-light represents a runtime with some minimal set of web apis generally found across edge runtimes. However some environments might be both edge-light compatible and node compatible and (node is adding many web APIs) and when both conditions exist we want to favor the node implementations. A followup to this change will add the web streams APIs to Flight and Fizz so the node version exports the same interfaces for web streams that edge does in addition to the node specific implementations.
2023-07-06 10:50:59 -07:00
"node": "./static.node.js",
"edge-light": "./static.edge.js",
Standardize condition order so that edge-lite preferred over browser (#29877) The export maps for react packages have to choose an order of preference. Many runtimes use multiple conditions, for instance when building for edge webpack also uses the browser condition which makes sense given most edge runtimes have a web-standards based set of APIs. However React is building the browser builds primarily for actual browsers and sometimes have builds intended for servers that might be browser compat. This change updates the order of conditions to preference specific named runtimes > node > generic edge runtimes > browser > default
2024-06-12 15:31:23 -07:00
"browser": "./static.browser.js",
Add entry points for "static" server rendering passes (#24752) This will be used to add optimizations for static server rendering.
2022-06-18 22:34:31 -04:00
"default": "./static.node.js"
},
[DOM] disallow client entrypoints with react-server condition (#28784) `react-server` precludes loading code that expects to be run in a client context. This includes react-dom/client react-dom/server react-dom/unstable_testing react-dom/profiling and react-dom/static This update makes importing any of these client only entrypoints an error
2024-04-08 15:37:06 -07:00
"./static.browser": {
"react-server": "./static.react-server.js",
"default": "./static.browser.js"
},
"./static.edge": {
"react-server": "./static.react-server.js",
"default": "./static.edge.js"
},
"./static.node": {
"react-server": "./static.react-server.js",
"default": "./static.node.js"
},
"./profiling": {
"react-server": "./profiling.react-server.js",
"default": "./profiling.js"
},
Add exports field to react-dom (#23252) This configures the exports field for react-dom. Notably there are some conditions for the /server entry point where we pick the export based on environments. Most environments now support Web Streams which is preferred in those environments. We already do this using the "browser" field so the "browser" condition applies here too. I don't think it's necessary, but I also specified "worker" explicitly since this is for Service Workers and those are often targeted with Web Pack's "webworker" target, which is also what Cloudflare currently recommends. I also added "deno" but deno is a bit special because this only works if you run with the node compatibility since otherwise you have to specify absolute URLs for the imports.
2022-02-08 17:19:52 -05:00
"./test-utils": "./test-utils.js",
[DOM] disallow client entrypoints with react-server condition (#28784) `react-server` precludes loading code that expects to be run in a client context. This includes react-dom/client react-dom/server react-dom/unstable_testing react-dom/profiling and react-dom/static This update makes importing any of these client only entrypoints an error
2024-04-08 15:37:06 -07:00
"./unstable_testing": {
"react-server": "./unstable_testing.react-server.js",
"default": "./unstable_testing.js"
},
[ServerRenderer] Move fizz external runtime implementation to react-dom-bindings (#25617) <!-- Thanks for submitting a pull request! We appreciate you spending the time to work on these changes. Please provide enough information so that others can review your pull request. The three fields below are mandatory. Before submitting a pull request, please make sure the following is done: 1. Fork [the repository](https://github.com/facebook/react) and create your branch from `main`. 2. Run `yarn` in the repository root. 3. If you've fixed a bug or added code that should be tested, add tests! 4. Ensure the test suite passes (`yarn test`). Tip: `yarn test --watch TestName` is helpful in development. 5. Run `yarn test --prod` to test in the production environment. It supports the same options as `yarn test`. 6. If you need a debugger, run `yarn debug-test --watch TestName`, open `chrome://inspect`, and press "Inspect". 7. Format your code with [prettier](https://github.com/prettier/prettier) (`yarn prettier`). 8. Make sure your code lints (`yarn lint`). Tip: `yarn linc` to only check changed files. 9. Run the [Flow](https://flowtype.org/) type checks (`yarn flow`). 10. If you haven't already, complete the CLA. Learn more about contributing: https://reactjs.org/docs/how-to-contribute.html --> Following [comment](https://github.com/facebook/react/pull/25437#discussion_r1010944983) in #25437 , the external runtime implementation should be moved from `react-dom` to `react-dom-bindings`. I did have a question here: I set the entrypoint to `react-dom/unstable_server-external-runtime.js`, since a.) I was following #25436 as an example and b.) `react-dom-bindings` was missing a `README.md` and `npm/`. This also involved adding the external runtime to `package.json`. However, the external runtime isn't really a `react-dom` entrypoint. Is this change alright, or should I change the bundling code instead? ## How did you test this change? <!-- Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes the user interface. How exactly did you verify that your PR solves the issue you wanted to solve? If you leave this empty, your PR will very likely be closed. -->
2022-11-03 11:15:29 -04:00
"./unstable_server-external-runtime": "./unstable_server-external-runtime.js",
Remove deprecated wildcard folder mapping (#23256) * Remove deprecated folder mapping Node v16 deprecated the use of trailing "/" to define subpath folder mappings in the "exports" field of package.json. The recommendation is to explicitly list all our exports. We already do that for all our public modules. I believe the only reason we have a wildcard pattern is because our package.json files are also used at build time (by Rollup) to resolve internal source modules that don't appear in the final npm artifact. Changing trailing "/" to "/*" fixes the warnings. See https://nodejs.org/api/packages.html#subpath-patterns for more info. Since the wildcard pattern only exists so our build script has access to internal at build time, I've scoped the wildcard to "/src/*". Because our public modules are located outside the "src" directory, this means deep imports of our modules will no longer work: only packages that are listed in the "exports" field. The only two affected packages are react-dom and react. We need to be sure that all our public modules are still reachable. I audited the exports by comparing the entries to the "files" field in package.json, which represents a complete list of the files that are included in the final release artifact. At some point, we should add an e2e packaging test to prevent regressions; for now, we should have decent coverage because in CI we run our Jest test suite against the release artifacts. * Remove umd from exports Our expectation is that if you're using the UMD builds, you're not loading them through a normal module system like require or import. Instead you're probably copying the files directly or loading them from a CDN like unpkg.
2022-02-09 11:37:17 -08:00
"./src/*": "./src/*",
"./package.json": "./package.json"
Add exports field to react-dom (#23252) This configures the exports field for react-dom. Notably there are some conditions for the /server entry point where we pick the export based on environments. Most environments now support Web Streams which is preferred in those environments. We already do this using the "browser" field so the "browser" condition applies here too. I don't think it's necessary, but I also specified "worker" explicitly since this is for Service Workers and those are often targeted with Web Pack's "webworker" target, which is also what Cloudflare currently recommends. I also added "deno" but deno is a bit special because this only works if you run with the node compatibility since otherwise you have to specify absolute URLs for the imports.
2022-02-08 17:19:52 -05:00
},
Use single entry point for SSR via browser field (#10362) * Use single entry point for SSR via browser field * Add server.browser entry point and smoke tests * Tweak bundle naming * Fix import * Re-record * Fix the robot nits * Add resetModules for some extra isolation
2017-08-03 00:41:09 +01:00
"browser": {
Add entry points for "static" server rendering passes (#24752) This will be used to add optimizations for static server rendering.
2022-06-18 22:34:31 -04:00
"./server.js": "./server.browser.js",
"./static.js": "./static.browser.js"
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
}
Bump next prerelease version numbers (#32782) Updates the version numbers in the prerelease channels.
2025-03-28 16:20:04 -04:00
}
Reference in New Issue Copy Permalink