-
-
Notifications
You must be signed in to change notification settings - Fork 606
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
Escape Characters in CSS content not processed correctly #459
Comments
@rjnair-nm for getting started did an earlier version of |
@michael-ciniawsky I had tried using css-loader 0.25.0 with webpack 1 and that used to work fine. I was upgrading to webpack 2 and while using the latest version of css-loader with that, i came across this issue. |
@rjnair-nm While copy and paste, maybe typo while you opened the issue maybe the root cause 😆 .icon-caret-left:before {
content: “\F10C"
}
|
The delimiters don't match |
Otherwise I need webpack 1 && webpack 2 configs + ideally a small test repo for each to debug 😛 |
@michael-ciniawsky I am using a custom library like Bootsrap which has the class definition as below :-
When the webpack processes this via css-loader, it transforms to : -
Webpack rule for css :-
I see this issue #87 which was raised here. But in that case it was removing the escape characters, but in my case its adding extra escape characters 😄 |
kk, as a 'workaround' would it be possible to reference bootstrap as static asset in meantime and exclude it from the bundle ? Also could you test another decl if it happens there also and a maybe pattern comes up when and where 😛 ? |
@rjnair-nm added tests #493, seems for one escaped characters all works fine, maybe problems in some |
I'm having this same issue without postcss. I'm running sass-loader right into css-loader and getting similar output.
outputs as
|
For anyone still having this issue I've created a temporary fix locally using a custom loader.
custom loader
This is most likely highly tailored to my specific situation but you should get the jist. Just use a simple custom loader to run some cleanup on the css-loader output for now. |
Close in favor #578 |
…ling issues were around webpack defect webpack-contrib/css-loader#459. To temporarily get around this, I've moved all theme-specific styles/images into public directory as static resources and linked directly from <head>.
@zaneadix I used your way to customize one loader for my issue, which is about a special character in css content (e.g. ü inside of |
I am using css-loader and i could see that the content is not being processed correctly.
Original CSS :-
The above CSS was processed by webpack to :-
Webpack: 2.2.1
CSS-Loader: 0.27.3
Node: 7.2.1
The text was updated successfully, but these errors were encountered: