Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Vue-masonry not working in Internet Explorer 11
See original GitHub issueHi, I have setup and used vue-masonry in my Nuxt project. Everything works fine in browsers like Chrome and Firefox. It doesn’t work in Internet Explorer 11. Do you know how to solve this? It gives a error message:
Script1014: Invalid character
vendors.app.js (69040, 21)
Screenshot:
Thanks in advance
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Is your Vue app not working in IE 11? Here's how to fix it.
The main reason why your Vue app is breaking in IE11 is because the browser does not support modern JavaScript syntax.
Read more >Compiling ES6 and VUE JS not working in IE 11
I wanted to provide a complete view of everything I used to transpile ES6 to ES5, add polyfill promises and async functions, which...
Read more >vue-masonry - npm
Start using vue-masonry in your project by running `npm i vue-masonry`. ... Since v 0.11.3 in-browser usage is available using a direct ...
Read more >Offline First Masonry Grid Showcase with Vue
This is what a masonry grid looks like: An offline app showing the grid of images. The app will be built with Vue,...
Read more >IE 11 is not working well for VUE JS
In all browsers my code is working well but in IE 11 is creating problem. Some output is not coming. ... // (runtime-only...
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
@jhlee8804 the change bw 0.11.7 and 0.11.8 are
@hyperst8 can you confirm that using 0.11.7 solves the problem? then we could act accordingly - update README, create a PR to fix that inconsistency
v0.11.7 working now. But v0.11.8 is not working on IE11.