vuetifyjs / vuetifyjs/nuxt-module
[BUG] SSR not dynamic according to Nuxt routeRules
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 286
- Forks
- 35
- Avg merge
- 5d 21h
- Merged PRs (30d)
- 4
Description
My Nuxt3 app has the base SSR config enabled ssr: true, but then I have Nuxt routeRules to disable SSR in specific routes like the following:
routeRules: {
'/test/**': {
ssr: false,
},
},
However, this module seems to only enable/disable SSR according to the base configuration, and is ignoring whether SSR is enabled for a specific route or not.
Meaning, if I access any page inside /test, and for example use useDisplay from Vuetify, it will show that SSR is enabled. If I disable SSR in the base nuxt config, then when using useDisplay it shows SSR as disabled.
Expected behaviour
The module should update the SSR configuration dynamically depending on whether that route that SSR enabled or not, just like Nuxt does.
Actual behaviour
Module is fetching the SSR configuration from the global base nuxt config and is ignoring whether SSR is enabled/disabled for a specific route.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the module reads the global Nuxt SSR setting and how Nuxt applies routeRules for the /test/** route. Verify the behavior with useDisplay on a route under /test and on a route without that rule; done means the module's SSR state matches Nuxt's route-specific setting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nuxt, typescript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100