Closed esiao closed 8 years ago
Sorry to say it, but you should ask postcss-import developers.
Unfortunately they always use default CSS parser and it is not a best strategy.
@TrySound do you have any plans to load files with different parser based on file extension?
@ai For this case we have easy-import stuff.
However not based on extensions.
I think we should a bit more extend postcss-import API and include different parsers in easy-import.
@TrySound can you send a PR with postcss-easy-import notice to project README?
@esiao You didn't apply parser, which is postcss option, not .pipe
.pipe(postcss(plugins), {parser: sugarss})
@TrySound that was it... Sorry for the inconvenience. I now have a different issue linked to nesting but it's not related to this plugin.
Using sugarss parser with postcss-import or precss (postcss-partial-import) fails. Both plugins are complaining about missing semicolons and won't import the file.
Since sugarss gets rids of the semicolon for the best I would say that it may be a mater of execution ? sugarss parser should be executed before the postcss plugins ? Or am I doing something wrong ?
Kind of error thrown :