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

Chunks not being created with TypeScript : [FLUSH CHUNKS]: Unable to find default in Webpack chunks. Please check usage of Babel plugin #60

Open
aneogiarcadix opened this issue Jun 13, 2018 · 4 comments

Comments

@aneogiarcadix
Copy link

I get this error in a Typescript project of mine. So I cloned the universal-demo project and changed things to typescript( except server/index.js ). The project builds successfully, and then I get the same error.
image
What am I missing here? The only changes I have made to the webpack configs is adding at-loader to the rules and including ts and tsx to resolve extensions.

Current project structure:
image
tsconfig.json
{
"compileOnSave": true,
"exclude": ["node_modules"],
"compilerOptions": {
"noStrictGenericChecks": true,
"allowJs": true,
"declaration": false,
"noResolve": false,
"jsx": "react",
"module": "commonjs",
"target": "es2015",
"experimentalDecorators": true,
"sourceMap": true,
"noImplicitAny": false,
"noImplicitReturns": true,
"outDir": "./dist/",
"skipLibCheck": true,
"allowSyntheticDefaultImports": true,
"moduleResolution": "node",
//"types": [ "node" ],
"typeRoots": []
}
}

sample : https://github.com/aneogiarcadix/universal-demo-ts

@ScriptedAlchemy
Copy link
Collaborator

did it work before?

Why not upgrade to latest and use WP 4? every thing is much easier

@tstirrat15
Copy link
Contributor

@ScriptedAlchemy I'm actually seeing this problem on webpack 4 right now. My impression is that it has something to do with externalization: I encountered this problem when I went to fix my externals webpack configuration. When everything was included in the same server bundle, it worked fine; when I fixed the externalization, things broke.

@tstirrat15
Copy link
Contributor

The weird thing to me is that it's default. Is that referring to the webpack entrypoint, which would be the default for a module?

@tstirrat15
Copy link
Contributor

tstirrat15 commented Sep 18, 2018

Hmm... It also only shows up when I use webpack-node-externals, which seems strange to me. Why would that make a difference?

It's working fine when I use the example code for webpack externals configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants