-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
3.32.0 : TypeError: Cannot assign to read only property 'structuredClone' of object '[object global]' #1281
Comments
FYI, I believe this is node version specific - v18 works fine, but v19 + v20 don't. I presume they made |
You seem right, I deepdive in the gh actions history and I found this run where v18 works for the PR but not v19 and v20 : https://github.com/jean-humann/docs-to-pdf/actions/runs/5693855907/job/15510037805 |
If it helps, I believe it's specific to |
this zloirock/core-js#1281 is the issue we're facing. I'll set the node version for these integration tests to 18 for now
is this a bug on core-js or jest ? |
@sibelius it's not a |
…one' (#174444) ## Summary @CoenWarmer found that `--watch` on jest tests will cause this sort of error: ``` TypeError: Cannot assign to read only property 'structuredClone' of object '[object global]' ``` There's some workaround suggested on this thread (although not necessarily related): zloirock/core-js#1281 In the workaround, we set `structuredClone` to `{}`, this would allow the currently offending 3rd party to overwrite it where it's currently getting an error.
The workaround to fix `structuredClone` type error in jest.config.js was found in zloirock/core-js#1281 and came from elastic/kibana@a5dbf26 Change-Id: I18163a5b7fd0a25cc3d65b69d25499c32e8614ca GitOrigin-RevId: 19b1612b23f2dfb75f0fb6b8c3ab9a7323609bd1
…one' (elastic#174444) ## Summary @CoenWarmer found that `--watch` on jest tests will cause this sort of error: ``` TypeError: Cannot assign to read only property 'structuredClone' of object '[object global]' ``` There's some workaround suggested on this thread (although not necessarily related): zloirock/core-js#1281 In the workaround, we set `structuredClone` to `{}`, this would allow the currently offending 3rd party to overwrite it where it's currently getting an error.
…one' (elastic#174444) ## Summary @CoenWarmer found that `--watch` on jest tests will cause this sort of error: ``` TypeError: Cannot assign to read only property 'structuredClone' of object '[object global]' ``` There's some workaround suggested on this thread (although not necessarily related): zloirock/core-js#1281 In the workaround, we set `structuredClone` to `{}`, this would allow the currently offending 3rd party to overwrite it where it's currently getting an error.
this zloirock/core-js#1281 is the issue we're facing. I'll set the node version for these integration tests to 18 for now
Hello
core-js
community ✋,I'm using
core-js
in my jest test hereThe test were working fine till dependabot open this PR to update version to 3.32.0
I have a new error in the jest test with 3.32:
Cf: https://github.com/jean-humann/docs-to-pdf/actions/runs/5808871705/job/15746546250?pr=157
Could you have a look please ?
The text was updated successfully, but these errors were encountered: