-
Notifications
You must be signed in to change notification settings - Fork 309
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
[Feature]: TextEncoder polyfill #1914
Comments
For reference, the workaround to polyfill
|
Also having this issue with Angular 15.1. We are using an Nx monorepo and multiple libraries just started failing because of this issue. The workaround from @Timebutt works, but it requires us to patch all our currently failing libs and future libs until this is made compatible. We already have |
@alextrep96 I have the same setup and it's really frustrating issue. I thought I was the only one having the problem. Somehow relieving to not be the only one with the issue 😅 |
@SimenB is this something Jest can take care of in |
No, we're waiting for upstream support. We've had lots of issues with added polyfills before, so I don't wanna add any more |
🚀 Feature Proposal
Include some kind of polyfill/patch suggested in jsdom/jsdom#2524
Motivation
With angular 15.1 a breaking change was introduced (angular/angular#48748) so that TextEncoder is now needed. This breaks tests in an jest + jsdom env.
While jsdom does not support TextEncoder angular test with jest will fail.
Example
No response
The text was updated successfully, but these errors were encountered: