-
Notifications
You must be signed in to change notification settings - Fork 84
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
Using inline-css in React #87
Comments
I would suggest changing the title to 'Using inline-css in React' first to get more visibility to this issue. I haven't tested it with webpack, only gulp. And I wouldn't expect it to work with React as it only works with HTML in the page at runtime, not the HTML injected into the page at runtime. It could potentially work with Gatsby or Next.js, or something that uses pre-rendering. |
Is this issue about literally using I am interested in the first case, but I'm not sure if I should +1 this issue or create a new one. FWIW: Attempting to import
|
I changed the title to match the original question. How this module is integrated with React is up to us I guess. |
If I'm not mistaken, this project aims to remove inline style tags from HTML and put them in CSS file. This would be enormously helpful if it worked with React and Webpack because it would automate CSP policy by enforcing no inline style tags exist! So this is a really great thing. @jonkemp do you know if such automation exists or could exist? Inline style tags are super convenient, but CSP exists for a reason and inline style tags should never exist in production code! If this or some such pre-processor could stuff all inline tags into CSS files that would be amazing. UPDATE* This is what I was looking for: https://github.com/tailwindlabs/tailwindcss |
Hi,
I want to use exact same functionality that is presented in this repo in front-end side (React project). Can this library do that for me? Because as I tested it doesn't work for in project (webpack doesn't get built). Any suggestions?
Thanks
The text was updated successfully, but these errors were encountered: