-
-
Notifications
You must be signed in to change notification settings - Fork 210
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
TypeError: Attempted to assign to readonly property #1188
Comments
Thank you for reporting @andyjessop! 🙂 It seems like your Typescript configuration is type checking the internals of Happy DOM which will cause problems like this. How does your tsconfig look? |
I believe this is a JavaScript |
I'm not sure how to reproduce this. Perhaps Axe or some other library is overriding the prototype of the |
I found this:
This might be hard to fix in Happy DOM, but should probably be fixed. |
…oot.adoptedStyleSheets to Window.getComputedStyle().
…ed-to-assign-to-readonly-property #1188@minor: Makes properties getters and setters in Node classes acc…
@andyjessop the issue has been fixed now 🙂 You can read more about the release here: |
Amazing, thank you! |
Expected behaviour
Test:
Component:
I expect this should either pass or fail with a valid error.
Actual Behavior
I get this error:
Additional context
Bun 1.0.18
Happy DOM ^12.10.3
The text was updated successfully, but these errors were encountered: