Plugin gives errors in case of // comments

[keul]

Seems partially related to #33 or #46

Preamble: I migrated from old version 0.1.1 to 1.0.0-rc4 and a working application stopped working. I already read and performed migration procedure, converting class names and so on.

What I found: if my styled CSS contains comments in the form of // foo bar now I can't complile my app.

The errors is something like this:

ERROR in ./components/mycomponent.js
Module build failed (from ../node_modules/babel-loader/lib/index.js):
Error: ..../xxx.js.js: There was a problem adding namespaces to this CSS in the file .../xxx.js. Error: <css input>:7:3: Unknown word
 CSS:

If I go at line 7 of the CSS string I find a duble-slash.

I don't find any official reference, but I read that both of those kind of comments are legit:

  // This is a comment
  /* this is also a comment */

Unluckily now I have to convert my // to /* */.

[luanraithz]

Same doubt as this issue, I don't think that the problem is in this library, as the css passed to the postcss is right (right=exactly what the developer asked).

[keul]

Thanks @luanraithz. So the issue could be in the postcss dependency (I was not aware this project were using it), however as I know // is still perfectly valid for styled-components.
I'm wondering how styled-component is parsing on the front-end.

[luanraithz]

Oh, sorry, I didn't understand that styled-components already supported that syntax (as noted in the comment here).
So, that's probably better to add to this plugin as well.

Note: There are a few more inconsistencies with styled-compoents that make a little harder to use this plugin. Such as: #46