[Browser Support] Iconify/React 1.1.1 is not <= 11 compatible.
See original GitHub issuethe npm distributed bundle @iconify/react
is not presently being transpiled for backwards compatibility.
An example of said incompatibility can be found here: https://github.com/iconify/iconify-react/blob/master/src/icon.js#L62
Object.assign
is not compatible with IE less than Edge. Are there any plans to support older browsers like Iconify itself? Thanks in advance!
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
iconify/iconify-react: Iconify icon component for React - GitHub
It is a unified framework, aimed to offer all popular icon sets with one easy to use syntax: Font Awesome, Material Design Icons,...
Read more >Iconify for React
Currently Node.js does not natively support Fetch API. It is available in Node.js version 17 using flag "--experimental-fetch", but without it Fetch API...
Read more >85 - Stack Overflow
I found a way to fix it. Steps to fix: Open your package.json file and edit your browserslist as follows.
Read more >@iconify/react - npm
Iconify icon component for React.. Latest version: 4.0.1, last published: a month ago. Start using @iconify/react in your project by running ...
Read more >MOTIF Frequently Asked Questions
9)* Where can I find other FAQs related to Motif or X11? ... Motif 1.1.1 has been released as a patch to licensees...
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
@cyberalien - I would argue that you do not make concessions around your TS implementation. I would suggest that you major version the TS only / TS base (2.x instead of 1.x). Legacy support should be community driven and you should feel empowered to take your core project in the direction you see fit.
I realize this advice comes from the ether but Id be happy to help support backwards compatibility of newer iterations into ES5 compliant (or transpilable) code as much as possible to keep feature parity between the two.
Excellent!
I’m currently working on next iteration of Iconify, which is written in TypeScript. Unfortunately TypeScript uses
Object.assign
regardless of compile target and doesn’t transpile it to anything else, so I’ll just avoid using it. Compatibility with all users is more important than few saved bytes.