worker-loader | A webpack loader that registers a script as a Web Worker | Build Tool library

I figured out my problem,

Incorrect output block:

Do this:

Your problem may be related to this tweet.

Must update dependencies and clean.

It was syntax error. I just fixed the file name and it worked

I found myself in the exact same situation a few months back. I found a solution that worked for me, but first lets discuss why this is happening.

There are 3 layers here.

1. The development layer of your library
2. The build layer of your library
3. The application that consumes the build of your library

Layer 1 is simple. In whatever file you want to create a new worker, say its index.ts, you do your import X from "worker-loader!./X". Your index.ts knows exactly where to find your worker file. That's why things work on your webpack-dev-server.

Layer 2 is where things get weird. When you process the worker file with worker-loader, webpack outputs several files. Your config says filename: '[name].js', which would output a file for every file in your source folder, all on the same level in your _bundles folder. Webpack sees your import X from "worker-loader!./X", and it also sees your target name and location for the imported file, and the file doing the importing. It rewrites the location of the web worker file within the index.js output bundle to an absolute path relative to the rest of the bundle. You can control this more carefully by using the publicPath option in the worker-loader. But this doesn't really solve the issue, as you are only setting the publicPath as an absolute path, which leads us to step 3...

Layer 3, where you try to consume your package, is where things go wrong. You could never anticipate where one might try to import { makeAWorker } from 'your-library' in their code. Regardless of where they import it, the build file (in the consumer app's node_modules) will be using the path that webpack wrote into the build of index.js to look for the worker file, but now the absolute path is relative to your consumer project (usually the home path, like where index.html lives), not to the node_modules folder of the build. So your consumer app has no idea where to find the worker file.

In my scenario, I decided that the content of my worker files was simple enough to create a worker from a string, and import it that way. For example, a worker file looked like this:

Just to bring to sight the answer given by Flash Thunder, the problem was my internet connection. I was using my phone to access the Internet. After connecting my computer to the closest wifi, everything is working fine

It looks like the cause of the function not being empty is your coverage tracker, thus the "cov" part of cov_10clr7afd6.f[9]++. This is one of the problems with inspecting any code that has gone through compilation steps, it might not be what you would reasonably expect.

Here's some options:

Looks like your situation is to be nested twice node_modules (node_modules/@opt-ui/icons/node_modules/@equinor/eds-icons), so you might have to set both @opt-ui and @equinor to re-transpile.

However, I have an idea which I'm not 100% the following way would work but it's worth trying though:

Actually, this issue is related to version of "@angular-devkit/build-angular".

For me works!

• After generating code sharing project:
  1. Drop folders: 'hooks', 'node_modules', 'platforms'
  2. Drop files: 'package-lock.json', 'webpack.config.js'
  3. Change version of '@angular-devkit/build-angular' from current (~0.803.0) to ~0.7.0 ; Then run npm install
  4. Then change '@angular-devkit/build-angular' version to current one (~0.803.0). Then run nmp install
  5. Test: tns run ios --bundle