No template for dependency: ConstDependency

[1234WoodMan]

No template for dependency: ConstDependency

[lzear]

I just ran into this issue with worker-plugin 5.0.0 in a Next.js app. yarn list showed 2 different versions of webpack. Using yarn selective version resolutions solved the issue in my case.

  // package.json
  "resolutions": {
    "webpack": "4.44.2"
  }

[thundermann]

I just ran into this issue with worker-plugin 5.0.0 in a Next.js app. yarn list showed 2 different versions of webpack. Using yarn selective version resolutions solved the issue in my case.

  // package.json
  "resolutions": {
    "webpack": "4.44.2"
  }

After adding your webpack resolution, make sure to run yarn install.

[SPKorhonen]

Seems to be duplicate of #27, no?

But as I commented there, please check if you have duplicate installs of webpack under your node_modules and dedupe them. It worked for me.

[developit]

What version of Webpack is this? The plugin only supports version 4. My guess is you're on 3 or 5.

[motiko]

I get the same error with webpack 4.42.0
/node_modules/next/dist/build/webpack/loaders/next-babel-loader.js

[developit]

If anyone can provide a bit more information here that would be useful. Since this is a version incompatibility, screenshots aren't enough to figure out where the problem lies.

[AtticusFetch]

Getting the same problem.
Happens inside a project built with NextJS, webpack version is 4.28.3, nextJS version is 7.0.2.
Checked node_modules, no duped webpacks there.
This is all info I have so far, not sure what else I could provide

[alvarovillafane]

@SPKorhonen I have the same issue you commented on #27 with Angular 9.

Can you explain to me how to update the Webpack versions in Angular 9 to make them equal?

I'm not seeing any versioning of webpack in package.json or in angular.json to update.

[alvarovillafane]

I just fixed in Angular 9 updating package.json to match a single webpack version across dependencies and then doing npm dedupe as explained in #58 (comment)

[developit]

I believe this may be fixed by 5.0.0?

[nickrttn]

I just ran into this issue with worker-plugin 5.0.0 in a Next.js app. yarn list showed 2 different versions of webpack. Using yarn selective version resolutions solved the issue in my case.

  // package.json
  "resolutions": {
    "webpack": "4.44.2"
  }

After adding your webpack resolution, make sure to run yarn install.

I'm still seeing this error with the suggested fix using resolutions, using package versions [email protected] and [email protected]. Downgrading Next.js to 10.0.5 does work, but isn't ideal. Does anyone have other suggestions for fixes or workarounds?

[lzear]

vercel/next.js#21740 (comment):

The resolutions no longer works as Next.js has webpack 4 + 5 inline now to allow for an easy opt-in in next.config.js

At this point, I don't see any other solutions than migrating to webpack 5, which seems to work for some people (vercel/next.js#22813).

[gustavomick]

this seems to be working for us on a similar case

new webpack.ProvidePlugin({
'L': 'leaflet',
}),