tslint-config-prettier | Use TSLint with Prettier without any conflict | Plugin library

kindly update the custom-webpack with ^12.1.3

Your production environment variables is missing REACT_APP_API_URL

My problem was that an another tsconfig file was overwriting the root's definitions, and turned off ivy and ngcc altogether.

sr5c/tsconfig.app.json:

You are not copying all of the source code in the second container, instead copying only one file, ie) server.js. Offending line is,

Not sure for what reason, the submit button inside form not triggered. Hence handled with external submit validation function.

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:

specifying

Solved this issue by installing brew and then doing brew install watchman on my mac.

The problem is in your command. Instead of -allow-dirty, it should be --allow-dirty (two leading dashes).