Source map broken with 3.1.0 -> 3.2.0

[oliviertassinari]

• I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

I would expect to see the source map in the dev tools of Chrome.

Current Behavior

Steps to Reproduce (for bugs)

With Material-UI:

1. git clone git@github.com:callemall/material-ui.git
2. cd material-ui
3. git checkout v1-beta
4. yarn
5. yarn docs:dev

Or with a simpler project: https://github.com/callemall/material-ui/tree/v1-beta/examples/nextjs.

Context

1. I have first noticed this issue on a project at work.
2. Hopefully, I was able to nail down the npm release that introduced the issue by a bisection between the v1.0.0-beta.6 release and v1.0.0-beta.7 release of Material-UI.
3. I'm also able to reproduce the issue on a simpler example, the nextjs example of Material-UI.

So, it's 3 independent projects impacted by the issue. I do think that it's a strong SNR ratio.

Your Environment

Tech	Version
next	v3.2.1
node	v8.1.4
OS	MacOs
browser	Chrome

[timneutkens]

Hey, this was fixed and will be in the next released 👌

[timneutkens]

@arunoda

[oliviertassinari]

:)

[ghost]

I am on 3.2.1 and this is happening to me. Perhaps I am not doing this right. Can some one point me to a proper webpack config? I has see multiple mentions that its enabled in "dev" by default. Some guidance would be appreciated. I am new to webpack and nextjs. I would be happy to share my teams webpack function in out next.config.js

[ghost]

Scratch that. Title is misleading. 3.2.2 solves.

[lock]

This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.