What about debugging?

[erykpiast]

The project seems super-interesting, I can't wait to try! But one question came to my mind - what about debugging? Did you consider sourcemaps generation? Or conditional (process.env.NODE_ENV !== 'production) expanding class names to readable form (like _xy132as_redButton). Do you plan anything like that?

[donaldpipowitch]

Source map support would be great. I think I wouldn't use stilr without Source maps.

[danieljuhl]

PR is very welcome. We will look into this, but I can't see exactly when, so any PR could speed up the process.

[aulizko]

PostCSS can create sourcemap.

I think this will be enough. It'll generate inline source map, which is fast and therefore completely OK for development IMO.

if (process.env !== 'production') {
  const prefixedCSS = postcss(autoprefixer())
    .process( StyleSheet.render(), { map: true} ) // <--- THIS
    .css;
  stylesheet.textContent = prefixedCSS;
}

As for production usage, you can generate separate source map, too. See the docs.

[boyswan]

would be great to expand on classnames, only problem I have with Stilr is hash only classnames!

[danieljuhl]

@boyswan sorry, but I do not understand, what you want. Can you please rephrase? You would like Stilr to not use hashes as classnames?

[boyswan]

At the moment classnames are generated as pure hashe's i.e. 'xy132as', it would be great if we could also include the actual classname, i.e. 'button_xy132as'

[danieljuhl]

Okay, so actually just a vote for the initial issue comment? PR is more than welcome.