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
Hi everyone,
I would like to understand how to handle updates for dependencies added by NX.
I know that the @nx/* and other packages are upgraded automatically by using the npx nx migrate latest but some packages are left behind.
For example, the Vite version installed in my monorepo by NX is v5.3.3. This version has a a vulnerability and should be upgraded. I have tried to upgrade NX to v20.1.3 but Vite is left behind despite the @nx/vite: 20.1.3 package has been installed.
Should I upgrade Vite or should the NX team upgrade it?
Who is in charge of handling these type of updates?
How can I check for example that @nx/vite: 20.1.3 supports the latest version of Vite available?
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
-
Hi everyone,
I would like to understand how to handle updates for dependencies added by NX.
I know that the
@nx/*and other packages are upgraded automatically by using thenpx nx migrate latestbut some packages are left behind.For example, the
Viteversion installed in my monorepo by NX isv5.3.3. This version has a a vulnerability and should be upgraded. I have tried to upgrade NX to v20.1.3 butViteis left behind despite the@nx/vite: 20.1.3package has been installed.@nx/vite: 20.1.3supports the latest version ofViteavailable?Beta Was this translation helpful? Give feedback.
All reactions