-
-
Notifications
You must be signed in to change notification settings - Fork 189
chore(rsc): release for react canary/experimental channel [not merge] #524
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
3c9ec2f
to
343a972
Compare
343a972
to
1f86064
Compare
Out of curiosity - is this needed anymore after #915 this one? |
Good point. I think it's fine to keep releasing preview, but we may tweak documentation to combine https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-rsc/README.md#canary-and-experimental-channel-releases and https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-rsc/README.md#react-server-dom-webpack |
Description
This is a dummy PR to (ab)use pkg.pr.new to release two nightly versions of
@vitejs/plugin-rsc
, which vendorreact-server-dom-webpack@canary
andreact-server-dom-webpack@experimental
instead of the default version[email protected]
.I created a workflow in my repo https://github.com/hi-ogawa/vite-plugins/blob/main/.github/workflows/trigger-nightly.yml, which pushes a commit to this PR everyday using my own fine-grained PAT.
These packages are for users who want to use React features which is only available on
canary
orexperimental
channel. Canary/experimental versions can be installed in a following way:Note that this is an interim solution and it's plan to have a clean separation of
react-server-dom-vite
and@vitejs/plugin-rsc
in the future. See the roadmap for more. (todo)