Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

New _tailwind route not compatible with i18n

See original GitHub issue

Version

@nuxtjs/tailwindcss: 3.3.1 nuxt: 2.14.9

Reproduction Link

Click on https://codesandbox.io/s/optimistic-noether-qko1j and navigate to /_tailwind in the CodeSandbox browser.

Steps to reproduce

Set up a fresh project with @nuxtjs/tailwindcss
Install nuxt-i18n into the project
Add config for nuxt-i18n (don’t know if this is required)

What is Expected?

No console output on navigation to /_tailwind.

What is actually happening?

The following error is printed to the console when accessing /_tailwind

 WARN  [vue-router] Route with name '_tailwind___en' does not exist

Issue Analytics

State:
Created 3 years ago
Reactions:3
Comments:6

Top GitHub Comments

1reaction

Atinuxcommented, Dec 8, 2020

I think that I am going to change this to use a serverMiddleware instead to bypass cue-router directly since it is only in dev

0reactions

rchlcommented, Dec 6, 2020

This is triggered by VueRouter because nuxt-i18n tries to lookup a non-existing route to see if it exists.

I can’t see any workaround or fix for it now. I believe fixing this would require fixing https://github.com/nuxt-community/i18n-module/issues/984 first. That would allow us to have a code path that avoids route resolving when we know for sure that route doesn’t exist.