-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automated tooling or way to auto adapt to this structure #3
Comments
Hi @apgapg! Yes. Makes sense. I will think about it. Do you have an idea about doing that? |
Some parts we can do automatically like registering components by writing a script. |
Maybe some webpack related configuration can help 🤔 |
@apgapg @rodolfo-santos with Nuxt 3's new module loading, the need to register the module is not loading existing. Check out my last commit. The module is loading loading automatically. What's left is the auto-registry of routes. I have mixed feelings about it. Do you think it is necessary? |
Hi @areindl ,
Thank you for this sample.
I was wondering if there's a way where we can extend nuxt core so as to auto read our new dir structure?
Currently we need to define our strategy in a module's index.js, which seems a little overhead everytime we define a new module.
The text was updated successfully, but these errors were encountered: