extract-loader | webpack loader to extract HTML and CSS from the bundle | Plugin library

I currently try to get the @microsoft/signalr npm package running with webpack and importing the module with import * as signalR from '@microsoft/signalr'. I get this error message which to my understanding boils down to webpack not being able to resolve the module-internal paths since all "missing" modules are part of signalr (I don't know how to call them). Running webpack shows this:

I have a pretty simple project which uses a couple of colours extended to the theme. When I enable purging in my tailwind.config.js file, everything is purged as they should, but all of my dark classes get purged too.

Does anyone have the same problem? I found an issue about this on tailwind's git as well: https://github.com/tailwindlabs/tailwindcss/discussions/2793

My resources are located in

I have this webpack.config.js:

I've put together my first, very simple Webpack config from scratch. In this I would like to bundle JS and also compile, minimize and autoprefix SCSS.

The code looks like this:

webpack.config.js

I have an application that is a node backend and a react frontend.

I get the following error when i try to build/run my node application.

Node: v10.13.0

Error:

dist/index.js:314 regeneratorRuntime.mark(function _callee(productId) { ^

ReferenceError: regeneratorRuntime is not defined

.babelrc

I have a new problem. I try to use material design (materiel.io) with Typescript and Webpack. First, I installed material with npm. Then, in one of my classes, I import @material/base.

edit: from another answer I decided to try upgrading from karma-webpack 3.0.5 to 4.0.0-rc.2, and I started getting actual errors. It started complaining that angular was not defined, and then I realized I was importing my home.spec.js file from the tests.bundle.spec file instead of relying on the context to import it (was doing this while debugging and forgot about it). After removing the extra import, my tests run successfully! I'll update this question with an answer once SO allows me to answer my own question.

I'm fairly certain that karma isn't even loading my test bundle file, although it seems that webpack creates the bundle.

I can't seem to see any console.logs from the tests.bundle.spec.js or home.spec.js files. When I have singleRun=false, and I check the console in the spawned Chrome window after a refresh (the tests should re-run), I see in the Network tab that the tests.bundle.spec.js file is loaded, but I see nothing in the console, and it's not referenced in the html file. The only scripts that are loaded in the html page are socket.io.js and karma.js.

edit: After opening the Debug page from Chrome, I do see my tests.bundle.spec.js bundle being loaded, but none of the included modules ever get run. I've put breakpoints into the test scripts, and even the tests.bundle.spec.js code (e.g. when setting the context for require) but none of the breakpoints ever get triggered. I must be missing something somewhere, because Karma never initializes any of these modules. I've even put breakpoints in the __webpack_require__ function, and they're not being triggered. So none of my modules are being required/imported.

Webpack definitely builds the module, and I see this in the output in the console from my yarn test command (which runs karma start):

I tried using matrial.io with webpack, just as described in material.io's getting started with the following configurations:

webpack.config.js --> exactly like example

Hello Guys I have a simple question I'm using webpack 4 to build a simple application

I'm trying to change the NODE_ENV variable automatically by using the dotenv package

I use many tricks to do this but nothing works.

please some help thank you...

this is my all config file please help guys thank you

webpack.config.js