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
3bb71dfd4bfc68920e758cd5fcf9fbfa44b99a21
react/packages/react-server-dom-webpack/package.json

68 lines
1.6 KiB
JSON
Raw Normal View History

[Flight] Move Flight DOM to a Webpack Specific Package (#17372) * Move Flight DOM to Webpack Specific Packagee We'll have Webpack specific coupling so we need to ensure that it can be versioned separately from various Webpack versions. We'll also have builds for other bundlers in the future. * Move to peerDep * Move DOM Flight Tests * Merge ReactFlightIntegration into ReactFlightDOM This was an integration test. We can add to it. * Fix fixture paths
2019-11-15 11:46:07 -08:00
{
[Flight] Rename react-transport-... packages to react-server-... (#20403) * Move files * Update paths * Rename import variables * Rename /server to /writer This is mainly because "React Server Server" is weird so we need another dimension. * Use "react-server" convention to enforce that writer is only loaded in a server
2020-12-08 08:08:57 -05:00
"name": "react-server-dom-webpack",
"description": "React Server Components bindings for DOM using Webpack. This is intended to be integrated into meta-frameworks. It is not intended to be imported directly.",
[Flight] Move Flight DOM to a Webpack Specific Package (#17372) * Move Flight DOM to Webpack Specific Packagee We'll have Webpack specific coupling so we need to ensure that it can be versioned separately from various Webpack versions. We'll also have builds for other bundlers in the future. * Move to peerDep * Move DOM Flight Tests * Merge ReactFlightIntegration into ReactFlightDOM This was an integration test. We can add to it. * Fix fixture paths
2019-11-15 11:46:07 -08:00
"version": "0.1.0",
"keywords": [
"react"
],
"homepage": "https://reactjs.org/",
"bugs": "https://github.com/facebook/react/issues",
"license": "MIT",
"files": [
"LICENSE",
"README.md",
"index.js",
[Flight] Add webpack plugin build (#18485) * Eject CRA from Flight We need to eject because we're going to add a custom Webpack Plugin. We can undo this once the plugin has upstreamed into CRA. * Add Webpack plugin build I call this entry point "webpack-plugin" instead of "plugin" even though this is a webpack specific package. That's because there will also be a Node.js plugin to do the server transform. * Add Flight Webpack plugin to fixture * Rm UMD builds * Transform classes * Rename webpack-plugin to plugin This avoids the double webpack name. We're going to reuse this for both server and client.
2020-04-03 14:04:56 -07:00
"plugin.js",
Rename react-server-dom-webpack entry points to /client and /server (#25504)
2022-10-18 10:15:52 -04:00
"client.js",
"server.js",
"server.browser.js",
"server.node.js",
Add Node ESM Loader and Register Entrypoints (#20274) * Add Node ESM loader build This adds a loader build as a first-class export. This will grow in complexity so it deserves its own module. * Add Node CommonJS regiter build This adds a build as a first-class export for legacy CommonJS registration in Node.js. This will grow in complexity so it deserves its own module. * Simplify fixture a bit to easier show usage with or without esm * Bump es version We leave async function in here which are newer than ES2015.
2020-11-16 23:46:27 -05:00
"node-register.js",
[Flight] Move Flight DOM to a Webpack Specific Package (#17372) * Move Flight DOM to Webpack Specific Packagee We'll have Webpack specific coupling so we need to ensure that it can be versioned separately from various Webpack versions. We'll also have builds for other bundlers in the future. * Move to peerDep * Move DOM Flight Tests * Merge ReactFlightIntegration into ReactFlightDOM This was an integration test. We can add to it. * Fix fixture paths
2019-11-15 11:46:07 -08:00
"cjs/",
Add Node ESM Loader and Register Entrypoints (#20274) * Add Node ESM loader build This adds a loader build as a first-class export. This will grow in complexity so it deserves its own module. * Add Node CommonJS regiter build This adds a build as a first-class export for legacy CommonJS registration in Node.js. This will grow in complexity so it deserves its own module. * Simplify fixture a bit to easier show usage with or without esm * Bump es version We leave async function in here which are newer than ES2015.
2020-11-16 23:46:27 -05:00
"umd/",
"esm/"
[Flight] Move Flight DOM to a Webpack Specific Package (#17372) * Move Flight DOM to Webpack Specific Packagee We'll have Webpack specific coupling so we need to ensure that it can be versioned separately from various Webpack versions. We'll also have builds for other bundlers in the future. * Move to peerDep * Move DOM Flight Tests * Merge ReactFlightIntegration into ReactFlightDOM This was an integration test. We can add to it. * Fix fixture paths
2019-11-15 11:46:07 -08:00
],
Add Node ESM Loader and Register Entrypoints (#20274) * Add Node ESM loader build This adds a loader build as a first-class export. This will grow in complexity so it deserves its own module. * Add Node CommonJS regiter build This adds a build as a first-class export for legacy CommonJS registration in Node.js. This will grow in complexity so it deserves its own module. * Simplify fixture a bit to easier show usage with or without esm * Bump es version We leave async function in here which are newer than ES2015.
2020-11-16 23:46:27 -05:00
"exports": {
".": "./index.js",
"./plugin": "./plugin.js",
Rename react-server-dom-webpack entry points to /client and /server (#25504)
2022-10-18 10:15:52 -04:00
"./client": "./client.js",
"./server": {
[Flight] Rename react-transport-... packages to react-server-... (#20403) * Move files * Update paths * Rename import variables * Rename /server to /writer This is mainly because "React Server Server" is weird so we need another dimension. * Use "react-server" convention to enforce that writer is only loaded in a server
2020-12-08 08:08:57 -05:00
"react-server": {
Rename react-server-dom-webpack entry points to /client and /server (#25504)
2022-10-18 10:15:52 -04:00
"node": "./server.node.js",
"browser": "./server.browser.js"
[Flight] Rename react-transport-... packages to react-server-... (#20403) * Move files * Update paths * Rename import variables * Rename /server to /writer This is mainly because "React Server Server" is weird so we need another dimension. * Use "react-server" convention to enforce that writer is only loaded in a server
2020-12-08 08:08:57 -05:00
},
Rename react-server-dom-webpack entry points to /client and /server (#25504)
2022-10-18 10:15:52 -04:00
"default": "./server.js"
[Flight] Rename react-transport-... packages to react-server-... (#20403) * Move files * Update paths * Rename import variables * Rename /server to /writer This is mainly because "React Server Server" is weird so we need another dimension. * Use "react-server" convention to enforce that writer is only loaded in a server
2020-12-08 08:08:57 -05:00
},
Rename react-server-dom-webpack entry points to /client and /server (#25504)
2022-10-18 10:15:52 -04:00
"./server.node": "./server.node.js",
"./server.browser": "./server.browser.js",
[Flight] Rename react-transport-... packages to react-server-... (#20403) * Move files * Update paths * Rename import variables * Rename /server to /writer This is mainly because "React Server Server" is weird so we need another dimension. * Use "react-server" convention to enforce that writer is only loaded in a server
2020-12-08 08:08:57 -05:00
"./node-loader": "./esm/react-server-dom-webpack-node-loader.js",
Add Node ESM Loader and Register Entrypoints (#20274) * Add Node ESM loader build This adds a loader build as a first-class export. This will grow in complexity so it deserves its own module. * Add Node CommonJS regiter build This adds a build as a first-class export for legacy CommonJS registration in Node.js. This will grow in complexity so it deserves its own module. * Simplify fixture a bit to easier show usage with or without esm * Bump es version We leave async function in here which are newer than ES2015.
2020-11-16 23:46:27 -05:00
"./node-register": "./node-register.js",
Test the node-register hooks in unit tests (#25132)
2022-08-24 19:05:39 -04:00
"./src/*": "./src/*",
Add Node ESM Loader and Register Entrypoints (#20274) * Add Node ESM loader build This adds a loader build as a first-class export. This will grow in complexity so it deserves its own module. * Add Node CommonJS regiter build This adds a build as a first-class export for legacy CommonJS registration in Node.js. This will grow in complexity so it deserves its own module. * Simplify fixture a bit to easier show usage with or without esm * Bump es version We leave async function in here which are newer than ES2015.
2020-11-16 23:46:27 -05:00
"./package.json": "./package.json"
},
[Flight] Move Flight DOM to a Webpack Specific Package (#17372) * Move Flight DOM to Webpack Specific Packagee We'll have Webpack specific coupling so we need to ensure that it can be versioned separately from various Webpack versions. We'll also have builds for other bundlers in the future. * Move to peerDep * Move DOM Flight Tests * Merge ReactFlightIntegration into ReactFlightDOM This was an integration test. We can add to it. * Fix fixture paths
2019-11-15 11:46:07 -08:00
"main": "index.js",
"repository": {
"type" : "git",
"url" : "https://github.com/facebook/react.git",
[Flight] Rename react-transport-... packages to react-server-... (#20403) * Move files * Update paths * Rename import variables * Rename /server to /writer This is mainly because "React Server Server" is weird so we need another dimension. * Use "react-server" convention to enforce that writer is only loaded in a server
2020-12-08 08:08:57 -05:00
"directory": "packages/react-server-dom-webpack"
[Flight] Move Flight DOM to a Webpack Specific Package (#17372) * Move Flight DOM to Webpack Specific Packagee We'll have Webpack specific coupling so we need to ensure that it can be versioned separately from various Webpack versions. We'll also have builds for other bundlers in the future. * Move to peerDep * Move DOM Flight Tests * Merge ReactFlightIntegration into ReactFlightDOM This was an integration test. We can add to it. * Fix fixture paths
2019-11-15 11:46:07 -08:00
},
"engines": {
"node": ">=0.10.0"
},
"peerDependencies": {
Bump versions for 17 (#20062)
2020-10-20 21:41:18 +01:00
"react": "^17.0.0",
Move react-dom implementation files to react-dom-bindings (#25345) This lets us share it with react-server-dom-webpack while still having a dependency on react-dom. It also makes somewhat sense from a bundling perspective since react-dom is an external to itself.
2022-09-28 19:05:50 -04:00
"react-dom": "^17.0.0",
update ReactFlightWebpackPlugin to be compatiable with webpack v5 (#22739)
2021-11-25 17:43:22 -05:00
"webpack": "^5.59.0"
[Flight] Move Flight DOM to a Webpack Specific Package (#17372) * Move Flight DOM to Webpack Specific Packagee We'll have Webpack specific coupling so we need to ensure that it can be versioned separately from various Webpack versions. We'll also have builds for other bundlers in the future. * Move to peerDep * Move DOM Flight Tests * Merge ReactFlightIntegration into ReactFlightDOM This was an integration test. We can add to it. * Fix fixture paths
2019-11-15 11:46:07 -08:00
},
"dependencies": {
Support named exports from client references (#20312) * Rename "name"->"filepath" field on Webpack module references This field name will get confused with the imported name or the module id. * Switch back to transformSource instead of getSource getSource would be more efficient in the cases where we don't need to read the original file but we'll need to most of the time. Even then, we can't return a JS file if we're trying to support non-JS loader because it'll end up being transformed. Similarly, we'll need to parse the file and we can't parse it before it's transformed. So we need to chain with other loaders that know how. * Add acorn dependency This should be the version used by Webpack since we have a dependency on Webpack anyway. * Parse exported names of ESM modules We need to statically resolve the names that a client component will export so that we can export a module reference for each of the names. For export * from, this gets tricky because we need to also load the source of the next file to parse that. We don't know exactly how the client is built so we guess it's somewhat default. * Handle imported names one level deep in CommonJS using a Proxy We use a proxy to see what property the server access and that will tell us which property we'll want to import on the client. * Add export name to module reference and Webpack map To support named exports each name needs to be encoded as a separate reference. It's possible with module splitting that different exports end up in different chunks. It's also possible that the export is renamed as part of minification. So the map also includes a map from the original to the bundled name. * Special case plain CJS requires and conditional imports using __esModule This models if the server tries to import .default or a plain require. We should replicate the same thing on the client when we load that module reference. * Dedupe acorn-related deps Co-authored-by: Mateusz Burzyński <mateuszburzynski@gmail.com>
2020-11-30 17:37:27 -05:00
"acorn": "^6.2.1",
[Flight] Basic scan of the file system to find Client modules (#20383) * Basic scan of the file system to find Client modules This does a rudimentary merge of the plugins. It still uses the global scan and writes to file system. Now the plugin accepts a search path or a list of referenced client files. In prod, the best practice is to provide a list of files that are actually referenced rather than including everything possibly reachable. Probably in dev too since it's faster. This is using the same convention as the upstream ContextModule - which powers the require.context helpers. * Add neo-async to dependencies
2020-12-07 12:10:18 -05:00
"neo-async": "^2.6.1",
Remove object-assign polyfill (#23351) * Remove object-assign polyfill We really rely on a more modern environment where this is typically polyfilled anyway and we don't officially support IE with more extensive polyfilling anyway. So all environments should have the native version by now. * Use shared/assign instead of Object.assign in code This is so that we have one cached local instance in the bundle. Ideally we should have a compile do this for us but we already follow this pattern with hasOwnProperty, isArray, Object.is etc. * Transform Object.assign to now use shared/assign We need this to use the shared instance when Object.spread is used.
2022-02-23 19:34:24 -05:00
"loose-envify": "^1.1.0"
[Flight] Move Flight DOM to a Webpack Specific Package (#17372) * Move Flight DOM to Webpack Specific Packagee We'll have Webpack specific coupling so we need to ensure that it can be versioned separately from various Webpack versions. We'll also have builds for other bundlers in the future. * Move to peerDep * Move DOM Flight Tests * Merge ReactFlightIntegration into ReactFlightDOM This was an integration test. We can add to it. * Fix fixture paths
2019-11-15 11:46:07 -08:00
},
"browserify": {
"transform": [
"loose-envify"
]
}
}
Reference in New Issue Copy Permalink