webpack 5.0.0-beta.30 Module not found: Error: Can't resolve '../../core-js/object/define-property' #11467
Comments
|
I'm having a very similar problem after upgrading from beta.29 to beta.30 but with this different import: Clearing the local filesystem cache ( |
|
I also encountered the same problem, which seems to be caused by enabling mjs experiments, and I did not find a way to close mjs experiments. |
|
These are all the same issues. In .mjs files or .js files with a package.json with That how ESM in node.js is defined, and you are opting in into this behavior by using the .mjs extension resp the field in the package.json. We didn't enforce this behavior in previous versions while this was still experimental in node.js, but it left this status, so I feel ok with enforcing this and pointing out these incorrect packages. You could disable that with |
|
@sokra I have extremely similar symptoms, even with the above I tried various positions of adding the rule, setting type in other potential rules involving .js/typescript that might affect it, but none solved this module not found issue. I suspect babel need to fix their code to support this correctly, otherwise there will be many people having issues with this on webpack5. For now I am sticking to |
|
After configuring like this, there will still be some modules can't resolve. const path = require('path');
module.exports = {
mode: 'development',
entry: { index: path.join(__dirname, 'src/index.js') },
devtool: 'source-map',
module: {
rules: [
{ test: /\.m?js/, type: "javascript/auto" },
{
test: /.*\.js$/,
type: 'javascript/auto',
exclude: /node_modules/,
use: [
{
loader: 'babel-loader',
options: {
presets: [
[
'@babel/preset-env',
{
targets: {
browsers: ['IE 11']
},
debug: false,
modules: false,
useBuiltIns: 'usage',
bugfixes: true,
corejs: 3
}
]
],
plugins: [
[
'@babel/plugin-transform-runtime',
{
corejs: { version: 3, proposals: true },
helpers: true,
regenerator: true,
useESModules: true
}
]
]
}
}
]
}
]
}
};import _asyncToGenerator from '@babel/runtime-corejs3/helpers/esm/asyncToGenerator.js';
function main() {
console.log(_asyncToGenerator);
}
main(); |
|
btw this is not an webpack-only error. If you run
Ok I tried that by myself and it doesn't work correctly. Instead you have to do that to change the resolving for these modules:
|
|
@sokra maybe we can put this option to https://webpack.js.org/configuration/resolve/ (by default with babel/ts/other loaders will increase the size an complex of configurations |
|
Also I think we need docs this /cc @chenxsan , can you open an issue? Maybe we should rewrite all |
thats how Node.js resolves.. Maybe we need to point in docs workaround.. |
|
@vankop yes, I known, in theory we can improve error messages out of box, like: Because now you might think something wrong with resolving (not found, etc) |
|
|
|
I also encounter similar issue but the message is like: To what I know this is an error when |
|
It's not forbidden. The import request need to be fully specified as |
On the latest beta of webpack 5 resolving fails with the below error and according to webpack/webpack#11467 is due to the imports in this module not being fully specified. This adds the config mentioned in the thread to correct the resolving for this module. ```sh Failed to compile. -- 16:33:50.046 | ModuleNotFoundError: Module not found: Error: Can't resolve './assertThisInitialized' in '/vercel/f03cc85/node_modules/@babel/runtime/helpers/esm' 16:33:50.046 | > Build error occurred 16:33:50.047 | Error: > Build failed because of webpack errors 16:33:50.047 | at build (/vercel/f03cc85/node_modules/next/dist/build/index.js:15:918) 16:33:50.099 | error Command failed with exit code 1. ```
|
Happening to me as well. Upgrading Webpack from beta.29 to beta.30, not doing literally anything else, breaks the build: |
|
Also seeing this issue with beta 30->32 as well, 29 still works ok. All of the errors we're getting are coming from Material UI via @babel/runtime. Adding the |
|
There is no problems on webpack side |
|
I'm not having luck with the And sometimes this one: The same issues don't happen on beta.29. Is anyone else seeing similar problems? |
|
@EvHaus Can you create reproducible test repo? |
|
/cc @vankop |
|
(webpack-internal:///./node_modules/next/dist/pages/_document.js:16:1) this error show in next js project |
# [1.1.0](v1.0.4...v1.1.0) (2023-01-30) ### Bug Fixes * **math:** Matrix3 subtract method and Matrix4 add/sub/multiply methods ([1f0fb3d](1f0fb3d)) * **math:** Matrix4 fromScale method ([0b6e49c](0b6e49c)) * **no-release:** fix build docs script ([a04dd66](a04dd66)) * **no-release:** plugin docusaurus webpack config to fix js resolve [webpack issues](webpack/webpack#11467) ([ad9dd6a](ad9dd6a)) * **Renderer:** add initialize default width/height ([629c8a8](629c8a8)) ### Features * **core:** add renderer resetState method ([4478e7f](4478e7f)) ### Performance Improvements * **core:** initialize gl parameter with auto ([3d00ffd](3d00ffd))
# 1.0.0 (2023-02-07) ### Bug Fixes * **core:** `Resource` subclass missing `removeStats` ([2a0e3f7](2a0e3f7)) * **core:** fix `Program` setStates method and update `Renderer` types def. ([a82fa00](a82fa00)) * **core:** fixed `Texture` magFilter state ([c10e56a](c10e56a)) * fix actions ci build docs dep ([0a428ef](0a428ef)) * **math:** `Matrix` and `Vector`、`Euler`、`Quaternion` toString method ([3eb2433](3eb2433)) * **math:** Matrix3 subtract method and Matrix4 add/sub/multiply methods ([1f0fb3d](1f0fb3d)) * **math:** Matrix4 fromScale method ([0b6e49c](0b6e49c)) * **no-release:** fix build docs script ([a04dd66](a04dd66)) * **no-release:** fix mapbox adapter workspace version and add readme doc ([f608e53](f608e53)) * **no-release:** plugin docusaurus webpack config to fix js resolve [webpack issues](webpack/webpack#11467) ([ad9dd6a](ad9dd6a)) * **patch:** disable adapters test ([04e16ce](04e16ce)) * **patch:** external gl-matrix and fixed docs build ([ce046f3](ce046f3)) * **patch:** fix actions ci build docs and refix external gl-matrix ([5ca130c](5ca130c)) * **patch:** fixed ci [release-adapters] ([eebdf51](eebdf51)) * **patch:** fixed ci [skip-ve-release] [release-adapters] ([34dfdfc](34dfdfc)) * **patch:** try release adapters in action ([1379d00](1379d00)) * **patch:** update mapbox adapter version ([b0c5793](b0c5793)) * **pitch:** Matrix identity and update docs ([382abfd](382abfd)) * **Renderer:** add initialize default width/height ([629c8a8](629c8a8)) * **utils:** gl util `isWebGL` and `isWebGL2` methods support maptalks grouplayer ([435f799](435f799)) ### Features * **adapters:** add maptalks adapter support ([dd62cf5](dd62cf5)) * **animation:** clock impl ([edef1cd](edef1cd)) * **animation:** raf impl ([79ab5c2](79ab5c2)) * **cameras:** base camera ([649b8ec](649b8ec)) * **cameras:** OrthographicCamera ([22a7771](22a7771)) * **cameras:** PerspectiveCamera ([0445307](0445307)) * **core:** `Renderer` resetState support reset `vao` and add `clear` method ([15f3079](15f3079)) * **core:** `Resource` support `swapHandle` and `restoreHandle` method ([cfa3d4d](cfa3d4d)) * **core:** add Program renderState options ([b0fa078](b0fa078)) * **core:** add renderer resetState method ([4478e7f](4478e7f)) * **core:** BufferAttribute ([35b7339](35b7339)) * **core:** Context and Resource and Texture ([ced2dc8](ced2dc8)) * **core:** core base ([ec5b2c4](ec5b2c4)) * **core:** EventEmitter ([96338c8](96338c8)) * **core:** Geometry ([ec0de76](ec0de76)) * **core:** Program ([e19164e](e19164e)) * **core:** Program ([b4554c8](b4554c8)) * **core:** RenderBuffer ([0ed53eb](0ed53eb)) * **core:** Renderer ([cef381f](cef381f)) * **core:** RenderTarget ([eb073d1](eb073d1)) * **core:** Shader class ([8e6da19](8e6da19)) * **core:** support mesh wireframe render and update docs, add Box geometry ([1b3252b](1b3252b)) * **core:** Texture3D support ([acb3b6d](acb3b6d)) * **core:** update Context ([d08ccb9](d08ccb9)) * **core:** update Context to Renderer, update Resource and Texture ([658979b](658979b)) * **core:** webgl renderer state ([2ae446d](2ae446d)) * **map-adapters:** add mapbox-gl adapter support ([45edb33](45edb33)) * **math:** Add `highPrecision` method to solve the problem of floating point calculation_ ([48bd74f](48bd74f)) * **math:** Color implementation ([458af7c](458af7c)) * **math:** Eular and Quaternion and Matrix4 Class ([73c3dda](73c3dda)) * **math:** Matrix Base and Vector Base Class ([a6f7e68](a6f7e68)) * **math:** Matrix3 and Vector2 Class ([ac4c120](ac4c120)) * **math:** Vector3 and Vector4 Class ([50a19e2](50a19e2)) * **object:** Mesh implementation ([1370e7a](1370e7a)) * **object:** Object3D and Scene ([7c64e63](7c64e63)) * **object:** Object3D and Scene ([188cf9e](188cf9e)) * **playground:** add demo and fixed docs ([566f929](566f929)) ### Performance Improvements * **adapters:** mapbox adapter default use high precision ([ff0b007](ff0b007)) * **ci:** update ci script ([b5c3591](b5c3591)) * **core:** initialize gl parameter with auto ([3d00ffd](3d00ffd)) * **core:** program render state update move to state ([6827107](6827107)) * **core:** Renderer request gl context, fixed default option ([7033101](7033101)) * **core:** update `Geometry` computeBoundingBox and computeBoundingSphere method support external `vertices` params ([64d18bb](64d18bb)) * **core:** update `State` reset method support `force` params ([98d0c58](98d0c58)) * **eslint:** format code ([89874ec](89874ec))
async@3 includes an ESM version dist/async.mjs, which Webpack by default prefers over the CommonJS version dist/async.js. Unfortunately, Webpack fails to compile the mjs version with the following error: ``` ERROR in ./node_modules/sharedb/node_modules/async/dist/async.mjs 61:25-32 Module not found: Error: Can't resolve 'process/browser' in './node_modules/sharedb/node_modules/async/dist' Did you mean 'browser.js'? BREAKING CHANGE: The request 'process/browser' failed to resolve only because it was resolved as fully specified (probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '*.mjs' file, or a '*.js' file where the package.json contains '"type": "module"'). The extension in the request is mandatory for it to be fully specified. Add the extension to the request. ``` This workaround suggested in webpack/webpack#11467 (comment) resolves the error, at least while Webpack supports the `fullySpecified: false` config.
async@3 includes an ESM version dist/async.mjs, which Webpack by default prefers over the CommonJS version dist/async.js. Unfortunately, Webpack fails to compile the mjs version with the following error: ``` ERROR in ./node_modules/sharedb/node_modules/async/dist/async.mjs 61:25-32 Module not found: Error: Can't resolve 'process/browser' in './node_modules/sharedb/node_modules/async/dist' Did you mean 'browser.js'? BREAKING CHANGE: The request 'process/browser' failed to resolve only because it was resolved as fully specified (probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '*.mjs' file, or a '*.js' file where the package.json contains '"type": "module"'). The extension in the request is mandatory for it to be fully specified. Add the extension to the request. ``` This workaround suggested in webpack/webpack#11467 (comment) resolves the error, at least while Webpack supports the `fullySpecified: false` config.
|
Can anyone solve this please... i am getting it in the browser console :)
|
and others
Bug report
What is the current behavior?
install
@babel/runtime-corejs3for file
index.jsand run
webpack ./index.jsbeta.29is working properly on this.but if we manually edit line 1 in file
./node_modules/@babel/runtime-corejs3/helpers/esm/defineProperty.jsfrom
to
and this issue goes away.
If the current behavior is a bug, please provide the steps to reproduce.
What is the expected behavior?
Other relevant information:
webpack version: 5.0.0-beta.30
Node.js version: 12.16.1
Operating System: win10 2004
Additional tools:
at the time I'm using
@babel/runtime-corejs3@^7.11.2The text was updated successfully, but these errors were encountered: