Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
esm-samples/webpack: npm start failed. ERROR in ./src/index.css
See original GitHub issueI am reporting an issue with
- TypeScript definitions
- another resource in this repository
Windows 10, Node v12.16.1
Do the following steps:
- Download the source code.
- cd esm-samples/webpack
- npm install
- npm run start
Encounter the error:
ERROR in ./src/index.css
Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js):
ModuleParseError: Module parse failed: Unexpected character ' ' (1:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#load
ers
(Source code omitted for this binary file)
...
79 ERRORS in child compilations
webpack 5.11.0 compiled with 80 errors and 2 warnings in 1408 ms
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
'npm start' returns error: "There might be a problem with the ...
In my case, I solved my problem in this way. create a .env at the root of the folder react folder; type SKIP_PREFLIGHT_CHECK=true...
Read more >ERROR in ./node_modules/css-loader!./node_modules/sass ...
My code works perfectly in dev environment when I try npm run build I get the following error: ERROR in ./node_modules/css-loader!
Read more >css-loader - npm
Start using css-loader in your project by running `npm i css-loader`. There are 16501 other projects in the npm registry using css-loader.
Read more >Getting Started with CSS Modules
js file we'll find an error when we run npm start again: That's the error that webpack will reveal if it can't find...
Read more >Error in running "npm run dev" - Laracasts
Running "npm run dev " gives the following error. ... at /var/www/html/work/node_modules/@tailwindcss/jit/src/index.js:50:11 at LazyResult.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
That’s what I meant. Let the app handle the loader rather than the plugin. That’s why I’m going to remove it.
Ahh, got it, thanks