A space to discuss and keep up software development and manage your software career
An inclusive community for gaming enthusiasts
News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more.
From composing and gigging to gear, hot music takes, and everything in between.
Discussing AI software development, and showing off what we're building.
A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here
Movie and TV enthusiasm, criticism and everything in-between.
Memes and software development shitposting
Web design, graphic design and everything in-between
A community of golfers and golfing enthusiasts
Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike
For engineers building software at scale. We discuss architecture, cloud-native, and SRE—the hard-won lessons you can't just Google
Discussing the core forem open source software project — features, bugs, performance, self-hosting.
A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other.
A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis.
A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more.
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 :)
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'] }
`
Awesome :D
Thanks for taking the time to try the code out :)
New feature :)
If you npm run serve the vue project with the terminal, it is opened and works both under IE11 and Chrome... But !
npm run serve
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 !
Interesting. I never tried serve option from the UI. Directly used the command line. So never came across this issue :)
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a blogging-forward open source social network where we learn from one another
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)
Not sure if this will work but worth a try :)
Solved but not working without the existing vue.config.js content. So, the following is working :
`
Awesome :D
Thanks for taking the time to try the code out :)
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 !
Interesting. I never tried serve option from the UI.
Directly used the command line. So never came across this issue :)