Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nested css classes disappear after running npm run build:prod #71

Closed
leonzinger opened this issue Jul 12, 2016 · 4 comments
Closed

nested css classes disappear after running npm run build:prod #71

leonzinger opened this issue Jul 12, 2016 · 4 comments

Comments

@leonzinger
Copy link

leonzinger commented Jul 12, 2016

I use nested classes in some of my css files like this:

.foo { & .nested {} }

and in the tsx file i use it like this:

`const s = require('./style.css');

div className={s.nested}
`

it runs smoothly in dev mode, but all of these classes disappear from the css after the build

@ericwooley
Copy link

It's the extract text plugin. I don't know why thats happening. But removing it fixed the problem.

Bummer though because thats a helpful thing to have.

I would investigate further, but I am doing a cordova app, have 0 extra time, and it doesn't affect me. Good luck!

@leonzinger
Copy link
Author

Thanks for the heads up!
On Wed, 31 Aug 2016 at 03:34 Eric Wooley notifications@github.com wrote:

It's the extract text plugin. I don't know why thats happening. But
removing it fixed the problem.

Bummer though because thats a helpful thing to have.

I would investigate further, but I am doing a cordova app, have 0 extra
time, and it doesn't affect me. Good luck!


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#71 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA0GeUD1NaCWRBeYdqds8uYEzJc_no6jks5qlMwIgaJpZM4JKHhG
.

@altaywtf altaywtf mentioned this issue Oct 29, 2016
5 tasks
@patroza
Copy link
Contributor

patroza commented Jan 16, 2017

This issue is fixed in this pull: #107

@altaywtf
Copy link
Contributor

hey @leonzinger @ericwooley can you guys try the latest version? @Sickboy did a great job with updating the dependencies and some config. It seems like fixed to me?

@altaywtf altaywtf closed this as completed Feb 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants