Nick Ribal

@albburtsev, there's this one too: https://github.com/vnovick/classNameGenerator

Hi @cristianbote and thanks for responding! Build or not isn't relevant, as far as I understand. Source maps merely point real, runtime identifiers to "virtual", original source files. The concept...

Not stale. I suggest we increase the grace period so avoid spamming everyone in issues like this one.

How about using something like [isomorphic-style-loader](https://github.com/kriasoft/isomorphic-style-loader), which is used in [react-starter-kit](https://github.com/kriasoft/react-starter-kit)? I'd happily work on a PR, but am not comfortable with isomorphic apps enough to give it a shot...

@birkir @strues @ctrlplusb can anyone more knowledgeable than me please have a look at my [suggestion above](https://github.com/ctrlplusb/react-universally/issues/322#issuecomment-282509422) to solve this without reinventing the wheel? :wheel_of_dharma:

@birkir, > I'm not a fan of isomorphic style loader HOC s method Can you please elaborate? I haven't tried using it myself, so don't have an informed opinion :(....

Thanks a lot @TrevorBurnham! I tried your setup and it indeed works, but with a couple extra dependencies: ```json "@stylelint/postcss-css-in-js": "^0.38.0", "postcss": "8.4.20", "postcss-syntax": "0.36.2", "stylelint": "^14.16.0", "stylelint-config-recommended": "^9.0.0", "stylelint-config-styled-components":...

Edit: it seems like this is actually another bug: https://github.com/styled-components/vscode-styled-components/issues/369 I'm leaving my comment here so anyone who lands here will find the right issue (and workaround) when the offending...

I've been using it for over a year now without issues. What are the issues you're referring to?

That's cause npm is already bundled with node itself. But if I understand correctly, one can use corepack to manage and enforce the exact version of npm. Haven't tried it...