IE 11 error: Object doesn't support this action

[devuxer]

I'm experiencing a perplexing error in Internet Explorer 11 (IE 11) when the following line is hit in this script:

var desc = Object.getOwnPropertyDescriptor(from, nextKey);

The error is:

SCRIPT445: Object doesn't support this action

It's not clear to me what object and action are being referred to in this message since Object.getOwnPropertyDescriptor has existed since IE 8.

I've pushed a github repo that reproduces this bug. Please see the README for additional details and screen captures from the debugger.

Steps to reproduce:

1. Clone the repo to your machine
2. Open a command line to the root directory
3. npm install
4. npm start
5. Open IE 11
6. Hit F12
7. Browse to localhost:3000
8. Note the errors in the console

(Note, you must have node installed on your machine)

[devuxer]

After a lot Googling, I think the error I'm getting is probably caused by this: ljharb/es-abstract#39

[ljharb]

Looks like this is an issue in this repo's broken Object.assign polyfill - Object.getOwnPropertyDescriptor(window.location, anything) crashes in IE 11.

Since Object.getOwnPropertyDescriptor isn't actually required for a correct polyfill - see https://github.com/ljharb/object.assign/blob/master/implementation.js#L12 specifically, for the most correct polyfill for Object.assign i'm aware of - this is a bug in this repo's assign polyfill.

[devuxer]

I can confirm that the "Object doesn't support this action" error went away when I switched from using polyfill.io to core-js, so @ljharb's comment appears to be the correct explanation.

[markcellus]

Still running into this issue. @ljharb what is the correct polyfill to use? Looks like your link went stale.

[ljharb]

@mkay581 the link works for me - https://npmjs.com/object.assign works as well.

[JakeChampion]

@mkay581 What is the polyfill.io url you are using and what browsers do you see this issue in? The related patch for this was added on 6th March, I'm wondering if you are seeing another bug/issue.

[markcellus]

Actually we went with another solution. So I'm unable to recall the details of the issue now. Sorry!