problem solving:
npm install -D babel-loader @babel/core @babel/preset-env webpack
Reference links:
https://github.com/babel/babel/issues/8599
Read More:
- Webpack — module build failed: error: the node API for ‘Babel’ has been moved to Babel core
- How to Fix webpack Module build failed Error: The node API for ‘babel’ has been moved to babel-core
- After NPM run dev is running, the browser does not respond and reports an error in. / ~ / Babel loader / lib! / ~ / Vue loader / lib/ selector.js?type=script&in
- Module build failed (from ./node_modules/postcss-loader/src/index.js):
- [Solved] This dependency was not found: * core-js/modules/es.error.cause.js in ./node_modules/@babel
- ERROR in ./node_modules/css-loader/dist/cjs.js!./node_modules/less-loader/dist/cjs.js!./src/css/spec
- Error in entry module not found: error: can’t resolve ‘Babel loader’
- Error: Cannot find module ‘@babel/core’
- Error: ‘default’ is not exported by node_ modules/qs/lib/ index.js
- About the solution of error: cannot find module ‘@ Babel / core’
- Module build failed: Error: ENOENT: no such file or directory, scandir，‘node_modules\node-sass\vend’
- [How to Fix] Cannot find module ‘babel-eslint‘
- Module parse failed:Unexpectedtoken (1:0)You may need an appropriate loader to handle this file type
- Module build failed: error:couldn’t find preset “env” relative to directory
- exception is java.lang.LinkageError: loader constraint violation: loader
- [Solved] gitbook: node_modules\npm\node_modules\graceful-fs\polyfills.js:287
- Error in Babel configuration of webpack
- Copy node causes NPM execution error: cannot find module ‘/ / lib / utils/ unsupported.js ‘
- The garbage plug-in mixed in chrome causes an error in the front-end JS operation: only one instance of Babel Polyfill is allowed
- 2021-07-03module parse failed: unexpected token (763:13) you may need an appropriate loader to