-
Notifications
You must be signed in to change notification settings - Fork 517
TypeError: chunk.isInitial is not a function #449
Comments
There's not enough information to debug. Which version of webpack/extract-text-webpack-plugin are you using? If you have webpack 1 and are using extract-text-webpack-plugin 2, that error could happen. In that case you'll have to use extract-text-webpack-plugin 1 or upgrade webpack to 2. |
I use last versions of 'extract-text-webpack-plugin' and webpack (2.2.1) |
Ok, still not enough info. Maybe someone else has a better idea. |
I don't know what else... It's just about a simple functionality - build 'bundle.css' from all css-files from project. What kind of information do you need? |
I would need a project to run. |
Maybe these lines?
|
Sorry, that doesn't help. I'm closing this issue until someone can provide a proper project to examine as instructed in the issue template. |
Unable to provide a project, but I'd just like to mention that this is happening to me also. Package versions:
Properties from config file:
Error when running webpack:
The same problem is also referenced here. I would submit a pull request but after bypassing this problem I receive another issue ( My proposed solution: |
@Rob-- Can you either upgrade to webpack 2 or downgrade the plugin to 1 series? I don't think the 2.x version of the plugin is supposed to work with webpack 1. That could be forced through a peer dependency. |
@bebraw I'm a complete idiot, for some reason I thought I was using Webpack 2.0 even though I saw my Webpack version was clearly not 2.0. It's working perfectly now, sorry for wasting your time! I did a clean install of Webpack and assumed it would download the latest version, instead it used an old version in my NPM cache. |
@Rob-- No probs. We may still want to set that peer dep to avoid these kind of issues. 👍 |
occurs for me as well - same exact issue same exact config. webpack : 2.2.1 |
@jony89 There's still not enough info to help. 😢 |
@bebraw what do you need? latest webpack, latest package of this module. add the following config to webpack : rules: [
{
test: /\.css$/,
loader: ExtractTextPlugin.extract({
fallback: 'style-loader',
use: [
{
loader: 'css-loader',
options : { autoprefixer: false, sourceMap: true, importLoaders: 1 }
},
'postcss-loader'
]
})
}
], and : plugins: [
new ExtractTextPlugin('index.css'),
] Then run the project with that webpack config and you will get :
|
@jony89 I would need a standalone project. Any chance you could open a separate issue with that? |
k |
see #461 |
@jony89 Ok. Hopefully someone can debug based on that. Thanks. |
@jony89 There is no |
@michael-ciniawsky so how do you expect me to provide a stand alone project? create one by your own, it is pretty easy. postcss is not needed to reproduce the issue. (I just tried to create standalone as fast as possible) this will trigger the same issue : rules: [
{
test: /\.css$/,
loader: ExtractTextPlugin.extract({
fallback: 'style-loader',
use: [
{
loader: 'css-loader'
}
]
})
}
], It start to look like you guys don't really want to try and fix that. I'm trying to help here.
you can open the zip, and see the files before you run them. |
@jony89 you could make a new repo and upload an example project there? |
@jony89 |
This is a little old now, but I just ran into this same error when I moved to a machine running node 7.0.0, after installing nvm and switching to 7.10.0 the error was resolved. webpack2.2 / extract 2.1 |
Same problem. All current stable versions: webpack 2.5.1 / extract-text-webpack-plugin 2.1.0. Just upgraded to node 7.10.0, still have the problem.
Edit: fixed by fixing webpack versions, see below |
some of the conversation moved to the issue, so i write my temp solution here as well:
this is the issue : #461 hope it helps for others. |
I thought I thoroughly checked all the versions, but it turned out I had a different webpack version running in node_modules of a higher level folder. So webpack was globally 2.5.1 but require('webpack') was an older version. Working fine now that I've got that sorted out. You can close this again |
Hello I am getting this error as well.
|
@elliotwesoff look at this html-webpack-plugin comment, it fixed my 'undefined' error (mainly back to webpack@2.6.1 or use npm@5) |
Hey @ghostd , I still get the same error after doing Is there a known working combination of webpack and node versions that I can use? Or even of this package's version? |
same issue here. jony89 comment helped me in my case, even though i'm using gulp-webpack, not webpack-stream as he states. Just to let you know: Basically, to make it work, try and provide to your webpack-stream or as in my case gulp-webpack webpack as a second param after your config ... that's what makes it work in my case as well :) |
Can't believe this issue still closed: node: 8.1.4 |
Hi! Can You review this article? You even don't need to know russian. Just execute commands and create files. I get topic error, when I execute What has forgotten the article author to do? |
Hi guys, I ran into this problem myself. After reading it I tried to downgrade the plugin to 2.1.0 and it works for me. So far I can say that 3.x didn't work with webpack 2.2.0. Hope this will help somebody here ;-) |
Thanks @marcopeg, I had the same issue. For me I was able to instead fix this issue by upgrading from webpack 2 to webpack 3. |
node: 8.4.0 the same problem... |
I am install local version webpack-dev-server and it solved the problem. |
I solved this issue by upgrading webpack-stream. webpack 3.5.6 |
Im having this situation with webpack 1.13.2 and extract-text-webpack-plugin 3.0.1 :/ |
for webpack 3npm install --save-dev extract-text-webpack-plugin for webpack 2npm install --save-dev extract-text-webpack-plugin@2.1.2 for webpack 1npm install --save-dev extract-text-webpack-plugin@1.0.1 |
@navasiloy your suggestion made the trick for my case. thanks. |
@webpack You definitely need another admin for this repository. |
@andrew-aladev please provide minimum reproducible test repo |
I was able to reproduce it with empty string as an extension for |
@andrew-aladev just ping me when repo is ready 👍 |
My chunks was created in It is an npm issue. It shouldn't be possible for me to install latest |
latest |
The problem was about |
There is this error:
I have no idea what is it.
My webpack.config.js file:
The text was updated successfully, but these errors were encountered: