Closed ghost closed 2 years ago
Same here
It looks like some stupid viruses I've seen. Idk why it spams "Liberty". It looks like it's trying to spam ascii art? and then some jargon which lags a bit.
Same problem here also I've been searching for solution for hours now. Don't know what is happening
This is the solution I am currently using myself for Live Server, I originally commented it in the issue thread under Colors.js: https://github.com/Marak/colors.js/issues/285#issuecomment-1007890688
Here's the same comment I posted there, might as well add it to this thread as well since it is also relevant here:
Alright, figured out how to temporarily fix the issue for use with Live Server.
The package.json
for Live Server has Colors.js set to use the newest possible version available, latest
, so I changed it back to the most recent Colors.js version that didn't have the issue, 1.4.0
. Just thought I'd share a fix for anyone else that may also run into this too 👍
comment the affected code.
Here's the image of it.
It look like some cringey virus code? spamming liberty?
Same here. Finally, I removed live-server dependencies.
Issue been solved #386, just waiting for an approval.
If anyone is interested, I forked this project and fixed it. You can use it the same way as original one. Link: https://www.npmjs.com/package/dead-server Good luck! ❤🚀🎅
As a quick fix, you can also just put colors
directly in your package.json
to override the live-server dependency
{
"dependencies": {
"colors": "1.4.0",
"live-server": "1.2.1"
}
}
Here's the image of it.
It look like some cringey virus code? spamming liberty?