Exception has occurred: TypeError: Cannot assign to read only property 'name'...
See original GitHub issueDescribe the bug
Exception has occurred: TypeError: Cannot assign to read only property 'name' of function 'function generateUUID(value, namespace, buf, offset) {
if (typeof value === 'string') {
value = strin...<omitted>... }'
How to reproduce
I’m not what to put here, this is throwing the error referencing my main JS file, but that file has no reference to the uuid functions.
Expected behavior
To not give this error lol.
Runtime
Node.js 14.15.5
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Cannot assign to read only property 'name' of object '[object ...
Show activity on this post. The following code will throw an error only for the name property. It could be fixed by specifying...
Read more >Cannot assign to read only property of Object in TypeScript
The TypeScript error "Cannot assign to read only property of object" occurs when we try to change a property of a frozen object...
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 '<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 >Cannot assign to read only property 'name' of function ' #2027
hi, it was working fine before, but I got this issue tonight This is the error: Cannot assign to read only property 'name'...
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 FreeTop 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
Top GitHub Comments
Is this really necessary? Even when not using v35 I get this super annoying error all the time when running with debugger
Same here, any way around it? I’m trying to connect to Cosmos DB with @azure/client and this is what happens as soon as I hot the API that I have there.