-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Breaking change after updating to 1.8.x (from 1.7.5) #2354
Comments
You should check out v1.8.5 pretty sure it fixed that |
Hey sorry to hear about this! Can you please provide a GitHub repo that reproduces the issue so we can more easily troubleshoot and diagnose the issue? |
Hey Adam, Thanks for the quick response. I cannot exactly share the repository but a regular angular 10 cli project + tailwind will have the exact same issues after build. I will try and do that if need be. One additional thing, this issue cannot be reproduced by running the project locally with the development webserver, it will only be an issue after the build (so perhaps test that using docker or a regular webserver). @benji014628, tried updating the package to the latest version (1.8.6), sadly we have the same issue. Caused by postcss-selector-parser trying to call a node util (deprecate) and as such, global.deprecate. This is what is causing the issue (from postcss-selector-parser):
|
Can you share a GitHub repository you create that reproduces the issue? It doesn't have to be your actual work project. Just something so I don't have to set it up from scratch myself. |
Hey @adamwathan, I created a repository and reproduced the issue. https://github.com/AlexanderOpran/angular-tailwind-debug Just run Funnily enough, in the larger project I can only reproduce this issue after the build not on local ( Please let me know if I can help with anything else. 😸 I tested every version available and it seems the issue starts appearing from version 1.7.6 onwards. |
Should be fixed in v1.8.8 👍 |
We have an Angular 10 project in which we are using TailwindCSS and we are also using resolveConfig. After updating to 1.8 we are getting a critical breaking change error (Uncaught ReferenceError: global is not defined). We have narrowed this down to the usage of the resolveConfig (if we do not use resolveConfig everything works fine even on 1.8). The error itself seems to be somehow related to the postcss-selector-parser package.
We can do a temporary workaround using things like:
(window as any).global = window;
in polyfills.ts but nevertheless, I do not think this should be an issue.
The text was updated successfully, but these errors were encountered: