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.
Bug of recognizing a JavaScript comment instead of URL
See original GitHub issueDoes this issue occur when all extensions are disabled?: Yes
- VS Code Version: October 2021 (version 1.62)
- OS Version: 21354.1
Here is a picture for contract:
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
POST url in JavaScript gets commented out - Stack Overflow
I'm trying to make a POST request in javascript, but URL's double slashes are treated as beginning of comment line.
Read more >What went wrong? Troubleshooting JavaScript - MDN Web Docs
Fixing syntax errors · Go to the tab that you've got number-game-errors. · This is a pretty easy error to track down, and...
Read more >A Definitive Guide to Handling Errors in JavaScript - Kinsta
Getting tripped up by errors in your JavaScript? We'll show you how to tame those errors so you can get back to developing...
Read more >uglify-js - npm
Start using uglify-js in your project by running `npm i uglify-js`. ... the X-SourceMap header instead, you can just omit sourceMap.url .
Read more >Node.js v19.3.0 Documentation
Instead, consider adding a comment next to the specific code path that should not throw and keep error messages as expressive as possible....
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
Seems like an issue with how we include javascript within the html grammar.
Thanks. Looks like
:is getting scoped asinvalid.illegal.newline.js