DEV Community

Discussion on: A quick introduction to Vue.js

 
drozerah profile image
Drozerah

Chrome is ok, I don't know about safari for now... There is an opened thread on the vue.js forum.

Thread Thread
 
drozerah profile image
Drozerah

Your remote url loads perfectly, that's not fair ! :)

Thread Thread
 
adityasridhar profile image
Aditya Sridhar • Edited

This is very weird :D

The same code is deployed in github pages.

Was just reading what is put in the forum.

Try adding this in vue.config.js ( you can delete the content in existing vue.config.js)

module.exports = {
  transpileDependencies: ['ansi-regex']
}

Not sure if this will work but worth a try :)

Thread Thread
 
drozerah profile image
Drozerah • Edited

Solved but not working without the existing vue.config.js content. So, the following is working :


module.exports = {
  baseUrl: process.env.NODE_ENV === 'production'
    ? '/vuejs-blog-demo-part1/'
    : '/',
  transpileDependencies: ['ansi-regex']
}


`

Thread Thread
 
adityasridhar profile image
Aditya Sridhar

Awesome :D

Thanks for taking the time to try the code out :)

Thread Thread
 
drozerah profile image
Drozerah • Edited

New feature :)

If you npm run serve the vue project with the terminal, it is opened and works both under IE11 and Chrome... But !

By using Vue UI serve task, the localhost returns a blanck page for both IE11 and Chrome, see the chrome terminal message bellow :

At the same, time the SCRIPT1002 message in IE is back :)

Conclusion :

Trust your terminal first !

Thread Thread
 
adityasridhar profile image
Aditya Sridhar

Interesting. I never tried serve option from the UI.
Directly used the command line. So never came across this issue :)