Skip to content

Firebase deploy and next build result in different root directory for post-css #72

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ifuller1 opened this issue Apr 21, 2023 · 1 comment

Comments

@ifuller1
Copy link

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.

@ifuller1
Copy link
Author

I managed to fix the issue by a) including the tailwind config location in and CSS modules b) extending the tailwind config to include ./hosting...

The cwd should be fixed though as I expect other side effects.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant