Andy VanWagoner

I would love for cssnext-loader to support running url() through webpack loaders, right now postcss-url custom url handler doesn't provide enough info to replicate what url-loader does. If I get...

If the url custom function got not just the url, but also the file path of the containing style sheet, then it should be fairly straightforward to run it through...

Also note that putting the css-loader to the right of cssnext-loader doesn't work properly because css-loader outputs javascript, which cssnext won't know how to handle.

That sounds simpler for the user. My only concern is trying to make sense of the resource. css-loader can handle js because its final output is js. If cssnext-loader outputs...

I spent some time trying to pass the urls through the webpack loaders and didn't have any luck getting it to work. I think for now, just getting the postcss...

The props for the top-level component are passed in by hexo depending on what is being rendered. You could try `this.props.post.content`, which I've seen as the main content for pages...

You may just need to add the following to index.js. Could you try it out? ``` hexo.extend.renderer.register('js', 'html', renderer, true) ``` I'm a little nervous about assuming every `.js` file...

This looks like the local context passed to the renderer isn't what it used to be. I'll have to dig up some time to look at this further.

If you aren't really using it either, then it probably would just be more work for you, and not necessarily any help to people who are using it. If no...

@magalhas Sorry about that. I've published it now as `1.0.1`.