Next.js: Object.keys non-object coercion not working in IE 11

[tomdohnal]

Bug report

Describe the bug

The argument passed to the Object.keys method should be coerced to an object from ES2015 onward.
As illustrated in the example taken from https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/keys.

// In ES5
Object.keys('foo');  // TypeError: "foo" is not an object 

// In ES2015+
Object.keys('foo');  // ["0", "1", "2"]     

However, this behaviour is not pollyfilled in Next.js for IE 11.

To Reproduce

1. Download the reproduction available at https://github.com/tomdohnal/object-keys-ie-repro
2. Use yarn dev or npm run dev to start the development server
3. Open the page in IE 11 and it crashes.

Expected behavior

It should coerce the argument passed to Object.keys to object and not crash.

System information

• OS: [Windows 10]
• Browser [e.g. IE 11]
• Version of Next.js: [e.g. 9.3.6]
• Version of Node.js: [e.g. 12.14.0]

[Timer]

Could you please test this on next@canary?

[tomdohnal]

I've just tested it and it's still broken on next@canary

[Timer]

Ooh, Object.keys exists in IE9 it seems. I do not believe we override existing browser globals to introduce new behavior. Let's take a deeper look into this though.

[tomdohnal]

Yeah it exists but lacks the coercion functionality which was added as a part of the ES6 spec...