facebook
Bug: `react-server-dom-esm` package is empty
I thought it would be helpful to use react-server-dom-esm for an RSC test integration, but the package appears to be empty for parking purposes.
Please consider publishing it as I'd prefer to use official implementations of servers to encourage testing practices that are supported by React. I'm also unable to build from source, it appears as the version of this package on main isn't in working condition outside of some internal fixtures yet.
Note: I originally thought this issue also applied to react-server-dom-webpack, but later realized I was installing the wrong channel, and that only the latest channel was empty. If there are resources to document this package, please clarify channel usage in the installation instructions.
React version: 18.3 (canary)
Steps To Reproduce
- Install
react-server-dom-esm -
import "react-server-dom-esm/server"; - Run with
node --conditions react-server
Alternative you can look up the code on npm, which has no JavaScript files.
The current behavior
Package fails to resolve modules because they're missing.
The expected behavior
Package contains code that can be imported and run.
having the same issue with react-server-dom-webpack. Looks like 2 days ago (8/4) a publish was made by @sebmarkbage for a version 0.0.1 which shows up as latest version to npm and only has an empty index.js and a package.json file in it.
https://www.npmjs.com/package/react-server-dom-webpack?activeTab=code
Now I'm getting this error while running build in a nextjs app. This didn't happen before.
Warning Babel parse has failed: This experimental syntax requires enabling one of the following parser plugin(s): "flow", "typescript". (13:7)
Not sure what the source of that error is specifically, but Next's app router already supports RSCs, so you don't need this package unless you're integrating a supplemental tool (like a test framework or story generator).
I later realized react-server-dom-webpack has working releases in its experimental and canary channels. If you're using react-server-dom-webpack, install react-server-dom-webpack@canary. The issue still remains for react-server-dom-esm.
@sebmarkbage Can you confirm if it's intentional or a misconfiguration? In #26889, you said it's just a proof-of-concept. So, I wonder if that's the reason.
Thanks, though I'm still keeping this open to track until there is a non-empty release.
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment!
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
bump
I think if react doesn't release esm version, react should delete that package
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment!
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment!
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment!
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment!
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you!