Cannot resolve module [object Object]

[raphaklaus]

Hi there! I'm trying to execute a webpack with extract-text, but I'm getting "Cannot resolve module '[object Object]'".

Here is a fragment.

    loaders: [{
      test: /\.css$/,
      loader: ExtractTextPlugin.extract({
        notExtractLoader: "style-loader",
        loader: "css-loader"
      })
    }]

Version of this plugin: 1.0.1
Node: 6.2.0. Tested in 4.4.0. And the same.

[raphaklaus]

Well, for some reason version 1.0.1 doesn't works with webpack 1.x
I've upgraded to extract-text-webpack-plugin@v2.0.0-beta.2 and webpack@v2.1.0-beta.19 and worked perfectly.

[Eschon]

Hi I'm having the same issue. I also use version 1.0.1 and my node version is 6.2.2.
Using v2.0.0-beta.2 or v2.0.0-beta.3 won't work for me because of #214

Here's the loader config for the plugin:

{
  test: /\.css$/,
  loader: ExtractTextPlugin.extract({
    fallbackLoader: 'style-loader',
    loader: 'css-loader!postcss-loader'
  })
}

Please let me know if I can supply any additional information for resolving this issue.

[Eschon]

I managed to fix it by changing my loader config to

{
  test: /\.css$/,
  loader: ExtractTextPlugin.extract('style', 'css-loader!postcss-loader')
}

Still I think there is an issue that should be resolved, because my initial config was pretty similar to what you have in the README.md

[Jessidhia]

You have to upgrade both extract-text-webpack-plugin to ^v2.0.0-beta.3 and webpack to ^v2.1.0-beta.19 to fix #214. ExtractTextPlugin.extract('style', 'css-loader!postcss-loader') only works at all on older extract-text-webpack-plugin.

[Eschon]

@Kovensky I know that #214 would have been fixed if I switched to the newest webpack beta but I don't like using beta versions of packages in production if I can avoid it.

And ExtractTextPlugin.extract('style', 'css-loader!postcss-loader') works without problems in extract-text-webpack-plugin@1.0.1

[narek11]

@Kovensky doesn't ExtractTextPlugin.extract accept only a single config argument ?

[Jessidhia]

@narek11 yes, as of the version 2 beta, and it complains at you if you do give more than one argument. Previous versions accept (up to) 3 arguments.

[arahansen]

I'm having this issue as well on webpack@1.13.1 and extract-text-webpack-plugin@1.0.1

I would rather not upgrade to either beta right now (upgrading webpack broke my build). Is there a workaround for this issue? Should I revert the plugin to an earlier version? @Eschon 's proposed fix didn't seem to do it for me.

[Jessidhia]

Use the documentation from the webpack-1 branch when using the 1.x version: https://github.com/webpack/extract-text-webpack-plugin/blob/webpack-1/README.md

[GarryFlemings]

I'm in exactly the same position as raphaklaus was Jul 17: Node 6.2.0, extract-text-webpack-plugin@1.0.1. When using the fragment he used, I got the same error message he got.

npm tells me to get answers at https://github.com/webpack/extract-text-webpack-plugin. Given that npm gave me v1.0.1, I followed the link to https://github.com/webpack/extract-text-webpack-plugin/blob/webpack-1/README.md. As I understood it, it told me to switch to the syntax Eschon used on Jul 25.

First, npm told me to install webpack-load-plugins. After that, npm went back to telling me to get answers at https://github.com/webpack/extract-text-webpack-plugin. So Eschon's syntax isn't working for me and I'm in the same position as arahansen on Jul 27: I need to use a stable release in production.

Do you have any idea of a condition that might have been present in Eschon's environment that I could reproduce and get this working? Is there a workaround? Thanks in advance.

[GarryFlemings]

New report. I got a workaround to work. See my documentation here.

[RyanCCollins]

I got into this same bind, wasn't able to update to the latest v of webpack and @Prairie-Falcon's guide saved me. Kudos!!

[ixcviw7bw]

Not sure if this will help, but in my case this was caused by having these lines in webpack config:

module.exports = {
  resolve: { fallback: path.join(__dirname, "node_modules") },
  resolveLoader: { fallback: path.join(__dirname, "node_modules") }}
...

Removing them fixed the problem.

[TNT-Likely]

@raphaklaus not work when i update extract-text-webpack-plugin to 2.0.0-beta.2,show errors

[alilland]

having issue with webpack v1.14.0 & extract-text-webpack-plugin v1.0.1 on windows when running webpack --watch within my react application .jsx file

// webpack.config.json
{
  // . . .
  module: {
     loaders: [
      {
        test: /\.jsx?$/,
        loader: 'babel-loader'
      },
      {
        test: /\.scss$/,
        loader: ExtractTextPlugin.extract({
          fallbackLoader: 'style-loader',
          loader: 'css-loader!sass-loader'
        })
      }
    ]
  },
  plugins: [
    new ExtractTextPlugin('./public/style.css')
  ]
}

Error output in terminal:

ERROR in ./src/Index.jsx
Module not found: Error: Cannot resolve module '[object Object]' in C:\Users\ALilland\Documents\application\src
 @ ./src/Index.jsx 15:0-26

[wheelerlaw]

@TNT-Likely Did you add the ExtractTextPlugin plugin to the list of plugins? Do something like this in your webpack.config.js:

config.plugins = [
    new ExtractTestPlugin('css/[name].[hash].css'),
    <other plugins>
]

@aronlmin You are using the wrong syntax for the extract method call. The syntax you are using is for the latest version of the extract-text-webpack-plugin. For version 1, change it to look like this:

loader: ExtractTextPlugin.extract('style-loader', 'css-loader!sass-loader')