Replies: 5 comments 2 replies
-
We would have a use case for shareable routes also. We are implementing several services with shared code. The shared code is shared through local npm packages. Currently, we have eight standalone endpoints and one svelte page (actually an error page ;) ) that are identical through every service. |
Beta Was this translation helpful? Give feedback.
-
Related: Adder ability, to add Hooks handle in sequence External Named Layout - from package |
Beta Was this translation helpful? Give feedback.
-
Theoretically loosely related (you have routes from the package, but not selected, but all at once): |
Beta Was this translation helpful? Give feedback.
-
Currently looking for a solution to this. I have things like user modules, payment modules, etc. Example :
|
Beta Was this translation helpful? Give feedback.
-
My case is that I need a page to be available at more then one route. I have a page with server code at |
Beta Was this translation helpful? Give feedback.
-
Since SvelteKit is a file-based router, I was wondering if there is some way to make routes shareable. I have a very specific use case for that myself, but let's use a more approachable example instead.
Let's say there is this awesome library for error pages, it's really descriptive, internationalized, and whatnot. It's attractive to use and people want to use it for their error routes. From my understanding, I would still have to create multiple routes and import modules in each of them.
Is this correct or is there an alternative I don't know about yet? I was hoping that advanced routing might offer something to solve this, but I don't see how.
Beta Was this translation helpful? Give feedback.
All reactions