Webpack 2.0 - Cannot read property 'unsafeCache' of undefined

Question

Webpack 2.0 - Cannot read property 'unsafeCache' of undefined

donaldpipowitch opened this issue 8 years ago · 16 comments

Please read right to the bottom of this thread for an approach that seems to work.

Using webpack@2.1.0-beta.23:

ERROR in ./src/index.tsx
Module build failed: TypeError: Cannot read property 'unsafeCache' of undefined
    at makeResolver (/Users/foo/node_modules/ts-loader/resolver.js:35:57)
    at ensureTypeScriptInstance (/Users/foo/node_modules/ts-loader/index.js:207:20)
    at Object.loader (/Users/foo/node_modules/ts-loader/index.js:387:14)

Used as:

export const tsLoader = {
  test: /\.ts(x?)$/,
  loader: `ts-loader?silent=true`
};

Answer 1 · 2016-09-20T19:38:20.000Z

+1 heeeelp

Answer 2 · 2016-09-20T19:43:34.000Z

I switched to https://github.com/s-panferov/awesome-typescript-loader. Works fine.

Answer 3 · 2016-09-20T20:58:02.000Z

I'm afraid ts-loader is untested with WebPack 2 to my knowledge. awesome-typescript-loader is probably the best choice if you're after WebPack 2.0 support now. Myself I haven't used 2.0 as it's still in beta (and 1 handles my use cases)

Answer 4 · 2016-09-21T16:38:36.000Z

For me, this only happens when I use the LoaderOptionsPlugin with an options key:

new LoaderOptionsPlugin({
  debug: false,
  options: { ... }
})

Remove options and it works fine. Fails even if options is an empty object literal:

new LoaderOptionsPlugin({
  debug: false,
  options: {}
})

Answer 5 · 2016-09-25T10:45:02.000Z

I tried awesome-typescript-loader and couldn't get it working so I decided to take a stab at figuring out how to fix this.

@r-park @johnnyreilly @donaldpipowitch @josiah1888 by console.loging in the place the error occured, I found that the options is actually the options from the LoaderOptionsPlugin. By doing this:

new LoaderOptionsPlugin({
  debug: false,
  options: {
    resolve: {}
  }
})

Everything runs again.

Answer 6 · 2016-10-09T04:24:48.000Z

Thanks @jeffijoe - we should probably include this in the docs somewhere to improve discovery. Well done for finding out!

Answer 7 · 2016-11-10T14:17:35.000Z

@jeffijoe: Thanks! That did the trick for me also!

Answer 8 · 2016-11-15T15:14:22.000Z

Also switched to awesome-typescript-loader. Any update when this will work again out-of-the-box without the workaround (which broke SASS for me)?

Answer 9 · 2016-11-15T15:32:58.000Z

The workaround isn't really a workaround as the resolver is not properly configured if you pass in an empty resolve object.

The issue is that when LoaderOptionsPlugin is used, the loader doesn't get the full webpack config but instead only what is contained within the object provided to LoaderOptionsPlugin.

Answer 10 · 2016-12-09T10:59:39.000Z

@jeffijoe Your workaround seems to work for me now without visible problems. But it would be great if the workaround wouldn't be needed.

Answer 11 · 2016-12-09T11:01:41.000Z

@donaldpipowitch Me too, this is how I feel about it:

Answer 12 · 2016-12-09T12:28:14.000Z

Would someone like to submit a PR to resolve this?

Answer 13 · 2016-12-09T22:21:53.000Z

Related docs: https://webpack.js.org/guides/migrating/#loaderoptionsplugin-context

Answer 14 · 2016-12-10T06:20:15.000Z

I've documented the workaround in the readme here: https://github.com/TypeStrong/ts-loader#webpack

Answer 15 · 2016-12-20T05:28:21.000Z

We now have an example in our examples section which demonstrates using ts-loader with webpack 2. I'm still not sure if the unsafe cache thing is actually a ts-loader issue; it feels like required configuration. FWIW in our example we supply all the webpack config options to the loader options plugin.

Answer 16 · 2017-02-06T07:57:11.000Z

The workaround is now documented on the readme and since this is for the Loader Options Plugin which is due to be short-lived I'm going to close this