-
-
Notifications
You must be signed in to change notification settings - Fork 874
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
plugin options are coming to be undefined #1909
Comments
Hi @fivethreeo , razzle has been working so well but recently, there are a few questions I need help with. I see the last update on this repo was around Oct. Are there any plans for improvements? Or active development in this repo? I might be missing something. Thanks! |
Razzle is dead, I started wazzle, but i am the only dev there aswell. So no progress there. Also there is rspack and turbopack. |
This is sad news @fivethreeo, I think I missed this announcement somewhere 馃槩 So is it ok to say that devs finding a few things difficult in Razzle now (like perf, version upgrades, etc) should right away look for the above-suggested alternatives? So that I don't keep visiting this repo every day to see if any activity happened 馃檲? |
Correct. |
馃悰 Bug report
Current Behavior
In the
![image](https://user-images.githubusercontent.com/15359575/215168550-65f803ca-7324-4ad5-b238-988c5eac9940.png)
modifyWebpackOptions
andmodifyWebpackConfig
, I want to update the plugin options but they are coming to be undefined.Expected behavior
Plugin options should have come
Additional context
I want to specifically toggle the
useBabel
ofrazzle-plugin-typescript
plugin conditionally but unable to do so.Your environment
The text was updated successfully, but these errors were encountered: