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
I use tailwind css and the @tailwind directives. They need to be included in a global.css file. To do this in Next13 you can import "globals.css". This import works fine in dev mode and using next build. However when using firebase deploy the non of the global CSS is included.
Adding a tailwind config to the post CSS config using a relative URL reveals that post-css in firebase deploy thinks it's running from the root firebase folder rather than the ./hosting folder. This results in a number of config related issues including an empty globals.css file.
The text was updated successfully, but these errors were encountered:
I use tailwind css and the @tailwind directives. They need to be included in a global.css file. To do this in Next13 you can import "globals.css". This import works fine in dev mode and using next build. However when using firebase deploy the non of the global CSS is included.
Adding a tailwind config to the post CSS config using a relative URL reveals that post-css in firebase deploy thinks it's running from the root firebase folder rather than the ./hosting folder. This results in a number of config related issues including an empty globals.css file.
The text was updated successfully, but these errors were encountered: