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
Since the release of Nx version 17, Nx officially supports Vue, and as they wrote in their release article:
Nx now provides a brand new Vue plugin that is being maintained by the Nx team! (And we're already working on a Nuxt plugin 🤫)
I was thinking whether the Nuxt CLI could leverage the Nx plugin system under the hood. It would lessen the maintenance of the CLI, because Nx already has a battle-tested way with its plugins to handle task executions and file generations.
Working with the Nx team would also create an opportunity to have a recommended way to develop larger Nuxt applications. The current default project structure is okay for small to medium-sized apps, but starts getting messy for larger ones. Larger apps need a feature-sliced structure, where every feature has its own components, hooks, etc. This was brought up during the Improved Directory Structure discussion briefly. The Nx team has been using this approach since the beginning with Angular, React and now with their Vue integration.
I'm not proposing Nuxt to rely tightly on Nx, but I see a lot of duplicated effort here:
developing a project scaffolding tool
coming up with a good project structure for large apps
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
-
Since the release of Nx version 17, Nx officially supports Vue, and as they wrote in their release article:
I was thinking whether the Nuxt CLI could leverage the Nx plugin system under the hood. It would lessen the maintenance of the CLI, because Nx already has a battle-tested way with its plugins to handle task executions and file generations.
Working with the Nx team would also create an opportunity to have a recommended way to develop larger Nuxt applications. The current default project structure is okay for small to medium-sized apps, but starts getting messy for larger ones. Larger apps need a feature-sliced structure, where every feature has its own components, hooks, etc. This was brought up during the Improved Directory Structure discussion briefly. The Nx team has been using this approach since the beginning with Angular, React and now with their Vue integration.
I'm not proposing Nuxt to rely tightly on Nx, but I see a lot of duplicated effort here:
If the two teams are not yet working together, I see a lot potential to do so.
Beta Was this translation helpful? Give feedback.
All reactions