Skip to content
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

CssSyntaxError with animation property #211

Closed
4ware opened this issue Jan 5, 2016 · 12 comments
Closed

CssSyntaxError with animation property #211

4ware opened this issue Jan 5, 2016 · 12 comments

Comments

@4ware
Copy link

4ware commented Jan 5, 2016

When i'm running the css-loader with the following code i get an error:

@charset "UTF-8";

.animated {
-webkit-animation-duration: 1s;
animation-duration: 1s;
-webkit-animation-fill-mode: both;
animation-fill-mode: both;
z-index: 100;
}

Module build failed: CssSyntaxError: /css-loader!/development/flot.to.web/node_modules/style-loader/index.js!/development/flot.to.web/node_modules/css-loader/index.js!/development/flot.to.web/css/animate.css:5:1: Unknown word

@psypersky
Copy link

Same here

@batwicket
Copy link

I'm also getting an error when '@charset' is parsed.

@gmaggess
Copy link

Has anyone found a fix for this?

@arufian
Copy link

arufian commented Mar 29, 2016

got same issue

@kincaidoneil
Copy link

I've also experienced this. Animate.css invokes it in the first line, so there's definitely the possibility many others are also encountering it. Any update on a potential fix?

@newbieYoung
Copy link

I have solved the problem by changing " require('css!./file.css') " to " import 'file.css' ".I guess when you use babel plugin and css-loader plugin you will meet the problem.

@Sugarball
Copy link

got same issue on normalize.css using import "css-loader!normalize.css"

@newbieYoung
Copy link

You should change " import 'css-loader!normalize.css' " to " import 'normalize.css' ". The right format is " import + path ".

@jkinzel-r7
Copy link

I'm getting this issue because we are compiling SASS including some vendor SASS that has the @charset at the top of the file. Any ideas on work arounds or fixes?

@delijah
Copy link

delijah commented Aug 17, 2016

Any news on this?

@alexander-akait
Copy link
Member

/cc @michael-ciniawsky maybe bug with old version postcss or old version in plugin for postcss which we used for parsing, but now error does not happen ⭐ . I think we can close this issue.
/cc @4ware @psypersky @batwicket @gmaggess @arufian @kincaidoneil @newbieYoung @jkinzel-r7 all works as expected now?

@michael-ciniawsky
Copy link
Member

Reopen if still any regressions with the latest version of plugins/loaders/webpack etc 😛

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