React version
Is the version of react locked in? I can see it's 17+ whereas the latest as we all know is 18+. I tried to set it to 18 with dependency rule in
.wasp
file like so
and got an error:
![No description](https://cdn.answeroverflow.com/1096375392211837008/image.png)
10 Replies
yes, some of the core packages (like React) are locked to what is Wasp using internally. I think we could actually upgrade, any reason @martinsos why we haven't yet?
is it possible to let developer control this? and ofc for those who don't care, wasp does things by default like it does now
yep, we actually could do that potentially! We could even support having multiple versions of the same lib, so you don't depend on what wasp uses
:boi:
Wohooo @IamIconLiving 🎄, you just became a Waspeteer level 1!
@IamIconLiving 🎄 is there any particular feature from React 18 you'd like to use?
for a todo app that I am putting together to discover wasp nope, but doing a production grade app I'd like to use latest stable versions of react
for sure! let us know how it went, would love to get your feedback 🙂
Wasp provides you with bits and pieces of React code and we need to know which React version we are targeting. And since the way the app is mounted changed from 17 to 18, we can't support both out of the box without making some changes internally. :/
That being said, we have a plan to upgrade to React 18 soon (next Wasp release probably) since it's not a big migration for us, but we do need to test everything well, to make sure that the whole DX is still good 🙂
absolutely @miho !
thanks for your responsiveness guys!