Joe Haddad

Yeah, this is a very valid problem. A light change in your code could alter the cascading effects of your CSS, so this is warranted. Maybe some docs on how...

It sounds like a bug, but this should be working. Can you give more details to reproduce this easily & some test files? A repo with README would be fantastic.

Thanks!

Hey, Next.js Core Team member here! We'd be interested in taking over maintenance of this package if you'd be willing to grant myself access to the repo and [npm](https://www.npmjs.com/~timer).

TypeScript is now officially supported as of Create React App 2.1. [Read the release notes to get started](https://github.com/facebook/create-react-app/releases/tag/v2.1.0)!

> So the version in your repo you made was an older one. Either way im not able to replicate this > > Are you sure youre using the latest...

I went ahead and explicitly upgraded the package to remove doubts: https://github.com/Timer/extract-css-chunks-webpack-plugin-bug/commit/39a5cb8b150b51577f5dfa32a5be2cc147867476

``` ❯ rm -rf node_modules && git rev-parse HEAD && yarn install && yarn why extract-css-chunks-webpack-plugin && yarn next build 39a5cb8b150b51577f5dfa32a5be2cc147867476 yarn install v1.21.1 [1/4] 🔍 Resolving packages... [2/4] 🚚...

@ScriptedAlchemy we no longer use this plugin in Next.js, so I'm not sure. The users who ran into this issue might know if it still reproduces: https://github.com/zeit/next.js/issues/10161

This behavior should've been fixed on Next.js 10.0.5+.