You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected behaviour: Development server should start properly upon executing a command
What actually happens is that following error gets thrown, and app gets stuck in loading state on localhost:
WARN [worker] Directory import '.../Projects/nuxt-bridge-with-tailwind-plugins/node_modules/tailwind-config-viewer/server' is not supported resolving ES modules imported from .../Projects/nuxt-bridge-with-tailwind-plugins/.nuxt/nitro/index.mjs
Did you mean to import tailwind-config-viewer/server/index.js?
Did you mean to import tailwind-config-viewer/server/index.js?
at finalizeResolution (internal/modules/esm/resolve.js:281:17)
at moduleResolve (internal/modules/esm/resolve.js:708:10)
at Loader.defaultResolve [as _resolve] (internal/modules/esm/resolve.js:819:11)
at Loader.resolve (internal/modules/esm/loader.js:89:40)
at Loader.getModuleJob (internal/modules/esm/loader.js:242:28)
at ModuleWrap.<anonymous> (internal/modules/esm/module_job.js:73:40)
at link (internal/modules/esm/module_job.js:72:36)
What I suspect of: First I thought it was config's module.exports, but it seems that this gets thrown internally from tailwind plugin. Even after changing require syntax to import, error is the same
@pi0 Why does it say in that discussion that tailwind module is supported for nuxt bridge then?
Also after setting viewer to false, when I navigate to another route, there's a FOUC for a second
Environment
Linux
v14.17.6
2.16.0-27226092.034b9901
Yarn
Webpack
head
,css
,plugins
,components
,buildModules
,modules
,build
-
@nuxtjs/tailwindcss@4.2.1
,@nuxt/bridge@3.0.0-27234503.d5127e9
Describe the bug and expected behavior
Expected behaviour:
Development server should start properly upon executing a command
What actually happens is that following error gets thrown, and app gets stuck in loading state on localhost:
First I thought it was config's module.exports, but it seems that this gets thrown internally from tailwind plugin. Even after changing require syntax to import, error is the same
Steps to reproduce
yarn install
yarn dev
and this error should pop upAdditional context
The text was updated successfully, but these errors were encountered: