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
TextDecoder seems to be incorrectly fatal=true by default? #30312
Comments
from the looks of your polyfilled source: next.js/packages/next/server/web/sandbox/polyfills.ts Lines 30 to 52 in a815ba9
it would seem to me that your version don't provide any valuable transformation or patching, so i'm wondering, why do you have a |
I'm closing this one because I couldn't reproduce at all. The reason for the wrapper was to hide certain APIs / exposed a configured instance but I think it is not providing any value at the moment so I've opened #31490 to remove it. Still, I could not reproduce the issue so I'll close it directly. |
This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
What version of Next.js are you using?
NaN
What version of Node.js are you using?
NaN
What browser are you using?
NaN
What operating system are you using?
NaN
How are you deploying your application?
NaN
Describe the Bug
Sry, if i could not give more information about the system/version being used (I'm in non direct contact of what you have built)
A user of
fetch-blob
reported to us that your polyfilled version of TextDecoder is buggy node-fetch/fetch-blob#118He said that when decoding a specific buffer that
new TextDecoder().decode(buf)
that it was throwing error when the defaultfatal
option is false.Expected Behavior
to not throw an error
To Reproduce
The text was updated successfully, but these errors were encountered: