Uncaught TypeError: Cannot assign to read only property 'for'...
See original GitHub issueJust came out of nowere. I’m getting the following error (Edge Version 104.0.1293.70):
Uncaught TypeError: Cannot assign to read only property 'for' of function '(template, ...values) => new Hole(type, template, values)'
at Function.assign (<anonymous>)
at tag (index.js:16:17)
at index.js:60:14
No need to mention this was working fine in previous versions of Edge/Chromium. Maybe they made read-only something that you are trying to override?
Issue Analytics
- State:
- Created a year ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Uncaught TypeError: Cannot assign to read only property
When you use Object.defineProperties , by default writable is set to false , so _year and edition are actually read only properties.
Read more >TypeError: "x" is read-only - JavaScript - MDN Web Docs
The JavaScript strict mode-only exception "is read-only" occurs when a global variable or object property that was assigned to is a read-only property....
Read more >Cannot assign to read only property of Object in JavaScript
The error "Cannot assign to read only property of object" occurs when we try to change a property of an object that has...
Read more >Uncaught TypeError: Cannot assign to read only property &
I have been using 4.8.x without problems. I am building mdbootstrap pro with webpack according to boilerplate description. Everything worked until I updated...
Read more >[Cannot assign to read only property '<field_name>' of object ...
This type of error(Cannot assign to read-only property) generally occurs on update of public property @api decorator variable value.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@WebReflection Thank you very much. No need to apology. Those are your libraries and I’m the one using them. They are all great, so, again, thank YOU.
@CheloXL please update
bind.for
to 0.2.0 which is fully tested as non-breaking for this, or any other, use case.Apologies for the inconvenience.