You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently upgraded from v17 to v18.0.5 and I have been comparing the default output from vite react mono workspace generators. One thing we noticed was the dotenv functionality seemingly stopped working. Our .env files were not being loaded. Looking closer, i believe it's because the newer generator is not adding explicit config to project.json to handle the Nx configuration to vite mode mapping. If I added this back in to project.json:
...the .env handling worked again. My larger question is what is the intent for Nx 18? Is the intent to use more convention-over-configuration? And if so, should I log this as a bug related to the generators for react and vite?
Is there an obvious location to see what the default configuration is meant to be?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Recently upgraded from v17 to v18.0.5 and I have been comparing the default output from vite react mono workspace generators. One thing we noticed was the dotenv functionality seemingly stopped working. Our .env files were not being loaded. Looking closer, i believe it's because the newer generator is not adding explicit config to project.json to handle the Nx configuration to vite mode mapping. If I added this back in to project.json:
...the .env handling worked again. My larger question is what is the intent for Nx 18? Is the intent to use more convention-over-configuration? And if so, should I log this as a bug related to the generators for react and vite?
Is there an obvious location to see what the default configuration is meant to be?
Beta Was this translation helpful? Give feedback.
All reactions