Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Uncaught TypeError: inspectSource is not a function #719

Closed
LukaszSawicki opened this issue Dec 6, 2019 · 6 comments
Closed

Uncaught TypeError: inspectSource is not a function #719

LukaszSawicki opened this issue Dec 6, 2019 · 6 comments

Comments

@LukaszSawicki
Copy link

Hi,
after update core-js to version 3.4.5 I've got an error when using Promise.all() function.

Uncaught TypeError: inspectSource is not a function at Object../node_modules/core-js/internals/native-weak-map.js at __webpack_require__ at Object../node_modules/core-js/internals/internal-state.js at __webpack_require__ at Object../node_modules/core-js/internals/redefine.js at __webpack_require__ at Object../node_modules/core-js/internals/export.js at __webpack_require__ at Object../node_modules/core-js/modules/es.promise.js at __webpack_require__

I can see that there was an 'fix' for inspectSource in 3.4.5
Fixed inspectSource helper with multiple core-js copies and some related features like some edge cases of Promise feature detection

Before this update everything worked fine.

@zloirock
Copy link
Owner

zloirock commented Dec 6, 2019

It was fixed in 3.4.7.

@zloirock zloirock closed this as completed Dec 6, 2019
@zloirock
Copy link
Owner

zloirock commented Dec 6, 2019

Or not? Could you check it?

@zloirock zloirock reopened this Dec 6, 2019
@zloirock
Copy link
Owner

zloirock commented Dec 6, 2019

Ok, I see one possible case - you use some copies of core-js, one of them - the previous version with broken inspectSource helper and your actual version inherit this helper. It's not a core-js bug, it's just a broken use case. However, I can add a workaround for that.

@LukaszSawicki
Copy link
Author

Okay, I found where the problem was: @babel/runtime-corejs3 was using an old copy of core-js-pure. Thanks for your answer.

@kamilic
Copy link

kamilic commented Dec 7, 2019

@zloirock This workaround works for me, what time you will publish this unreleased version?

@zloirock
Copy link
Owner

zloirock commented Dec 7, 2019

Soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants