-
-
Notifications
You must be signed in to change notification settings - Fork 17
Conversation
BREAKING CHANGE: It require vite>=1.0.0-rc.13. And user should install official react.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if we should check whether the package.json
of the root directory depends on react
or @pika/react
and use that.
I'm getting an error with this setup. Can you investigate? https://github.com/aleclarson/vite-sandbox/tree/react-34#readme |
You should add this to your vite.config.ts: I have opened a proposal to vite: let plugins define config "optimizeDeps" and "jsx". So that users don't need to manually define these option. |
I was trying to use React 17's new The I tried with and without |
|
Why would you put those in devDependencies? I'm gonna let @yyx990803 merge this one, so he knows to release a major version. I suggest you split the package.json changes into a |
So that we can use vite to develop npm library(.e.g a component library). |
@yyx990803 Could you merge and publish it when you are available? Thank you! |
Since vitejs/vite#837 is merged and released. We can use commonjs package like
react
andreact-dom
, and no longer need@pika/react
and@pika/react-dom
.Why I prefer
react
to @pika/react:@pika/react
doesn't sync all versions from official react. For example, 'experimental' versions.@pika/react
falls behind official react. It doesn't have17.x
by now !!BREAKING CHANGE: It requires vite>=1.0.0-rc.13. And user should install official react. I have already updated
package.json
in this PR.fix: vitejs/vite-plugin-react#20
fix: vitejs/vite-plugin-react#33
fix: vitejs/vite-plugin-react#31
fix: vitejs/vite-plugin-react#29