-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Installing tailwind causes app to throw #1111
Comments
@iwatakeshi Thanks for reporting this - I'm fixing this now. @thedavidprice This should go in |
Hey @iwatakeshi This fix will be in the next release which will be out shortly. |
@peterp Awesome thanks! I saw the changes in redwood/packages/core/config/webpack.common.js Lines 68 to 75 in 7b3a0be
options . I could be wrong but I think there should only be one since I just tried it locally by changing the config file manually and it worked.
|
@iwatakeshi Whoops, fixed now! |
@peterp Can you please take a second look on the fixes here? The tailwind generator (or tailwind for that matter) doesn't seem to work in development.
Tailwind seems completely broken now starting from v0.18. Even a manual install does not work. The generator also generates:
When it should be:
I provided some info which might help w/ tracing this: Willing to help w/ this but wanted to confirm that new projects using tailwind is indeed not working right now. I've tried generating 3 new projects on v0.19 and they're all broken as well. The app may startup, but tailwind styles are not being applied. |
I unfortunately confirm: it broke my styling on latest version bump. |
Issue might be related to #1170 |
Hi, I'm trying to install Tailwind via
yarn rw g util tailwind
. However, when I run the dev server usingyarn rw dev
, I immediately see an error message saying:This error even occurs in a new project. It could be just me, but here are the steps that I took:
yarn create redwood-app app
cd app
yarn rw g util tailwind
yarn rw dev
Doing a little search shows that it could be webpack but I'm not sure.
The text was updated successfully, but these errors were encountered: