[FLUSH CHUNKS]: Unable to find src/pages/PageManager in Webpack chunks.
See original GitHub issueHey guys,
Lately I’ve been encountering a weird log during build :
[FLUSH CHUNKS]: Unable to find src/pages/PageManager in Webpack chunks.
It shows pretty much after every template exported :
[FLUSH CHUNKS]: Unable to find src/pages/PageManager in Webpack chunks. Please check usage of Babel plugin.
Time to render to string and extract { '$$typeof': Symbol(react.element),
type: [Function: FinalComp],
key: null,
ref: null,
props: {},
_owner: null }
[FLUSH CHUNKS]: Unable to find src/pages/PageManager in Webpack chunks. Please check usage of Babel plugin.
[FLUSH CHUNKS]: Unable to find src/pages/PageManager in Webpack chunks. Please check usage of Babel plugin.
[FLUSH CHUNKS]: Unable to find src/pages/PageManager in Webpack chunks. Please check usage of Babel plugin.
Time to render to string and extract { '$$typeof': Symbol(react.element),
type: [Function: FinalComp],
key: null,
ref: null,
props: {},
_owner: null }
[FLUSH CHUNKS]: Unable to find src/pages/PageManager in Webpack chunks. Please check usage of Babel plugin.
[FLUSH CHUNKS]: Unable to find src/pages/PageManager in Webpack chunks. Please check usage of Babel plugin.
Time to render to string and extract { '$$typeof': Symbol(react.element),
type: [Function: FinalComp],
key: null,
ref: null,
props: {},
_owner: null }
[FLUSH CHUNKS]: Unable to find src/pages/PageManager in Webpack chunks. Please check usage of Babel plugin.
It doesn’t seem to affect the build, and the site works fine (even without JS on so html is being rendered correctly).
Any idea on what’s causing this ?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:12 (1 by maintainers)
Top Results From Across the Web
[FLUSH CHUNKS]: Unable to find default in Webpack ... - GitHub
I get this error upon server render. I have no clue what default is supposed to be. I have resolved the issue by...
Read more >webpack-flush-chunks - npm
This solves the problem of either having to make additional requests to get async components or React checksum mismatches when you do in...
Read more >Glossary - webpack
Chunk : This webpack-specific term is used internally to manage the bundling process. Bundles are composed out of chunks, of which there are...
Read more >tv-extract-css-chunks-webpack-plugin - npm package | Snyk
Every time your React component is rendered with those, CSS is generated and updated within the DOM. On the server, you're going to...
Read more >webpack-flush-chunks examples - CodeSandbox
Learn how to use webpack-flush-chunks by viewing and forking webpack-flush-chunks example apps on CodeSandbox.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Just realized that when those
FLUSH CHUNK
warnings appear, our built/exported site will flash white for a seconds upon loading (you see the static content, then when the JS app kicks in, the page render all white before re-rendering the content). This seems to appear right after the “Templates reloaded” console log appear. For us not changingconfig.paths.dist
removes the warnings, as well as the flash upon loading.Just checking if anyone has a solution for this issue?
We’re seeing the same issue (“you see the static content, then when the JS app kicks in, the page render all white before re-rendering the content”) as described by @nddery
Not using config.paths.dist is not an option for us I’m afraid. (We’re building inside a AWS lambda and only have write access to /tmp).
We’re indifferent about the “Templates reloaded” console.log appearing, but the white flash and re-rendering of content is an issue for us.
Thanks!