4.0.1 is not compatible with IE11
See original GitHub issueI’m not sure whether this bug report belongs here, or in the Nuxt repo, or in the @nuxtjs/axios repo…
With the latest version of Nuxt (2.15.5) and @nuxtjs/axios (5.13.1), an error is thrown when visiting a page in IE11, because defu is included in _nuxt/vendors/app.js, with the following code present (from node_modules/defu/dist/defu.mjs):
function _defu(baseObj, defaults, namespace = ".", merger) {
...
To reproduce:
- Follow the create-nuxt-app instructions at https://nuxtjs.org/docs/2.x/get-started/installation
yarn add install @nuxtjs/axios
- add
'@nuxtjs/axios'
tomodules
in nuxt.config.js yarn dev
oryarn build && yarn start
- Go to the server’s index page in IE11
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Fix site display issues with Compatibility View in Internet ...
When a site is incompatible with Internet Explorer 11 for Windows 7, you'll see the Compatibility View button Compatibility View button in the...
Read more >Compatibility problems with Internet Explorer 10/11 and an old ...
Problem is that framework 1.1 doesn't recognize Internet Explorer 10/11 as an advanced capability browser, so a lot of features (for example javascript...
Read more >Browsers and devices - Bootstrap
Bootstrap supports the latest, stable releases of all major browsers and platforms. On Windows, we support Internet Explorer 10-11 / Microsoft Edge.
Read more >Browser issues - Wagtail's documentation
IE11 ¶ · In Wagtail 2.11 (LTS), there was be a warning message displayed on the Wagtail dashboard for IE11 users with administrator...
Read more >Set Up Java for Internet Explorer - TechDocs
The only browser supports is Microsoft Internet Explorer 11. IE 11 is the only browser that still supports NPAPI, which RDP and SSH...
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
That is indeed the fix I came up with, but given that nuxt 2 DOES support IE11, I would not expect to have to transpile dependencies of nuxt/nuxt plugins/modules etc. - I would expect them to work without that.
On my side, I had to put axios back to “5.13.1” on
package.json
. I’ve been 3 hours now looking why our frontend broke, and it seems that using “^5.12.5” was enough to make axios load defu as a CommonJS dependency, thus breaking webpack (where es6 imports can’t be mixed with module.exports).I’m no expert on webpack nor defu, so if someone relates to what I’m explaining, this is the way I managed to fix a Nuxt deployment where the following error happened:
Cannot assign to read only property 'exports' of object '#<Object>'
on line:module.exports = defu;
Couldn’t understand what was happening as since many major versions that defu doesn’t use module.exports anymore, but transpile might be the reason that brings this bug back