Dynamic chunks not created when running next build twice

[tusbar]

Bug report

Describe the bug

Running next build twice will somehow not create the dynamic chunks on the 2nd run. Instead, the pages using the dynamic components (loaded using dynamic(import(…))) will all contain what should be included in the dynamic chunks.

Running a 3rd time makes the build fail.

To Reproduce

The issue is easily reproducible with the following repository: https://github.com/tusbar/next-js-dynamic-issue

1. rm -rf node_modules/.cache
2. next build, everything runs smoothly, generated bundles are correct.
3. next build again. The build runs faster thanks to hardsource, but the dynamic chunks are not created, the code from the dynamically imported components is moved to each of the pages using them.
4. next build again. The build errors with stuff like:

[hardsource:5dfb5712] Could not freeze ./components/dynamic-message.js: Cannot read property 'hash' of undefined

Expected behavior

2 sequential build should create the same bundles.

System information

• OS: macOs
• Version of Next.js: 7.0.0

[tusbar]

There are definitely some issues with hard-source-webpack-plugin:

• On cached builds, require.context modules are missing mzgoddard/hard-source-webpack-plugin#432
• TypeError: Cannot read property 'hash' of undefined mzgoddard/hard-source-webpack-plugin#416