As per #490 .defineProperty throws exception, but...
See original GitHub issueWhen you include the Intl polyfill, this polyfill already uses .defineProperty
with getter functions.
Therefore, although not having code with getter / setter codes, as described in #490, it’s failing because I included Intl in the requested bundle.
Is there any Intl implementation over there without using defineProperty
, or any other suggested solution?
Issue Analytics
- State:
- Created 7 years ago
- Comments:11 (7 by maintainers)
Top Results From Across the Web
Object.defineProperty() - JavaScript - MDN Web Docs
A TypeError is thrown when attempts are made to change non-configurable property attributes (except value and writable , if permitted), except ...
Read more >Object.defineProperty sometimes throws - Stack Overflow
I am playing with ES6 classes and non-writable properties. As an example, I have the following code. I am running it under node...
Read more >Unable to change window.location using Object.defineProperty
What is the expected behavior? The code should not throw an exception, and window.location.hostname === "example.com" should evaluate true.
Read more >TypeError: can't define property "x": "obj" is not extensible
In both, strict mode and sloppy mode, a call to Object.defineProperty() throws when adding a new property to a non-extensible object.
Read more >TypeScript: Assertion signatures and Object.defineProperty
The Object.defineProperty function either changes the object or throws an error should something go wrong. Exactly what an assertion function ...
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
I believe this issue can be closed now. I will create a new issue for the
detect.js
suggestion.Agreed.