[compatibility] version 4.6.9 broken on IE 11
See original GitHub issueYour Environment
- flatpickr version used: 4.6.9
- Browser name and version: IE 11
- OS and version: Windows 10
Looks like it’s because of polyfill for Object.assign
(node_modules/flatpickr/dist/esm/utils/polyfills.js) that uses spread operator ...
in function definition params:
"use strict";
if (typeof Object.assign !== "function") {
Object.assign = function (target, ...args) {
if (!target) {
throw TypeError("Cannot convert undefined or null to object");
}
for (const source of args) {
if (source) {
Object.keys(source).forEach((key) => (target[key] = source[key]));
}
}
return target;
};
}
Issue Analytics
- State:
- Created 3 years ago
- Reactions:9
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Fix site display issues with Compatibility View in Internet ...
Learn how to fix website display problems using Compatibility View in Internet Explorer.
Read more >Preventing K2 smartforms from running Compatibility mode ...
Compatibility mode in Internet Explorer is a feature that helps you view webpages that were designed for previous versions of the browser, ...
Read more >Determine if IIS/ASP.NET recognises IE 11 browser version
NET Framework to make it recognise the browser version, otherwise certain functionality may be broke. ASP.NET Doesn't Detect IE11.
Read more >Release notes for Windows - Zoom Support
The Initiate callback from Engagements tab enhancement was pulled from release due to compatibility issues, and will be available in another upcoming release....
Read more >Microsoft Internet Explorer 11 - Start Rule
On Tuesday, January 12th, Microsoft ends support for Internet Explorer 8, 9, and 10. The end of support means that these older versions...
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
From what I can tell, the problem is now package.json specifies
"module": "dist/esm/index.js"
, so if you’re doing bundling, it defaults to using that file (which contains the ES6 code)I got flatpickr working in IE11 by putting the following in my webpack config:
which tells webpack to specifically use the transpiled ES5-compliant file.
Hope that helps.
This kind of change needs to be documented properly (changelog / release-notes). Following semantic-versioning, this is even a breaking-change.