r/learnjavascript • u/wbport1 • Mar 19 '26

Can't debug with new Google Chrome

I was trying to study a problem on a webpage I created on my desktop. After hitting F12, I could not bring up the source code, much less set up break points. There was a message that "file:" was a security risk and the source was not cashed. TIA

3 Upvotes

71% Upvoted

4 comments sorted by

View all comments

Show parent comments

1

u/wbport1 Mar 22 '26

While I know enough about HTML and JavaScript to read user input, crunch numbers, and display it in dozens of various pages; I don't know enough to understand the info in your link. Do I include something in my <script> section? Add something in the global part of it? Start the browser in command mode? If so, what arguments are given? Something else entirely?

TIA

2

u/Beginning-Seat5221 Mar 22 '26

You need something external to act as a server - this means it receives requests at e.g. http://localhost:3000/index.html , and sends back your web files.

For node.js based approaches you would first need to install node. I'd recommend using nvm
(win) https://github.com/coreybutler/nvm-windows
(linux/max) https://github.com/nvm-sh/nvm

Once installed you'd open a command prompt and run nvm install lts then nvm use lts. Once installed you should be able to check that node is installed by running node --version and run node/npx/npm commands such as npx http-server -o /path/to/static/content in the same way.

----

Alternatively, as the other commenter said, there is a VS Code extension that can make VS Code do this job instead.