-
-
Notifications
You must be signed in to change notification settings - Fork 81
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
Allow creating multiple router instances #148
Labels
✨ feature request
a new feature request
Comments
posva
changed the title
[Feature Request] Subdomain support?
Allow creating multiple router instances
Apr 5, 2023
Thanks! Maybe this could be possible by allowing the plugin to be instantiated multiple times and exposing each of them via different module |
Oooo, yes that's actually a great idea in my opinion. Though, preferably we'd be able to add an alias such as: "vue-router/auto-chat" |
posva
added
⚡️ enhancement
improvement over an existing feature
✨ feature request
a new feature request
and removed
⚡️ enhancement
improvement over an existing feature
labels
Feb 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This package is amazing, though I think I may have a complicated use case to mess things up.
As of now, I have a laravel project with 3 subdomains, each has different routes available to them:
I need to be able to generate different route configurations for the subdomains independent of each other.
Excess information
For the purpose of development, I used this plugin with
routesFolder
to populate all 3 sets on all 3 subdomains.The issue is that the API doesn't serve routes outside of the subdomain. (e.g. calendar API doesn't work on chat pages).
Fine for development; however, for production a 404 should page appear instead.
What I'd prefer to be able to do, is add a route folder during runtime, so that each entry point only needs to add its specific routes.
Or even better, to be able to load this in the vite config somehow? (maybe through output.plugins?)
That being said, I can't imagine how this could be added to the output.plugins setting in a way that doesn't destructively merge.
As of now, if I try this, vite throws an error stating that vue-router/auto does not exist
The text was updated successfully, but these errors were encountered: