Replies: 1 comment
-
These may be of interest:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
During NuxtNation 2023 there was quite a few questions asked about layers, application structure, DDD etc.
I'm looking for some guidance. Still, after implemented several large sites in the last couple of years.
Let me first describe what am I looking for and how a typical project I work on look like: Imagine a set of websites or webapps that are very similar, but also different enough that it is not practical to only use configuration to differentiate them. On the other side the internals of those apps are quite complex. They have several features and each feature needs internationalization, data access layer, maybe authentication, documentation... All of the apps and features share some aspects - global ui components, eslint config, postcss config...
I think this is a well known problem space. For example monorepo tools like NX or Turborepo have a concept of
apps
andlibs
which correspond to what I have described above. The tricky part is how to structure all those libs. NX has some ideas about libraries like when to create them, how to name them, which type of lib should not be imported by other type etc.So what is challenging about this is how to actually implement this with Nuxt. Since we are talking about modular architecture - Nuxt modules come to mind. And while it looks like it is possible to do it (I am currently using Nuxt modules for everything in a monorepo with my team), it is not really straight-forward to do it. I will be using word lib for a building block or a as a generic word module.
What I'm missing specifically:
A couple of reasons why we should even care:
Other discussions around this topic:
I would like to collaborate on this topic if anyone is interested...
Beta Was this translation helpful? Give feedback.
All reactions