tnx for this, but I remember that up until recently I had a vs code where I could have easily without any cnfiguration see my code running on a browser (Chrome) How is it possible that I donb't have the option anymore?
I am encountering the same problem you are where I need to mention the complete address of the file in the settings file to actually run it. this is a work around not a solution, has anybody figured out a solution to this?
Can someone help me out. When I change the json settings and then try to run the code afterwards, I get the message " /bin/sh: start: command not found "
I think he didn't use the proper path that's why it showed "This site can’t be reached..........."...Just change the path to the suggestion above " cd $dir && start chrome && $dir$fileName" or "cd $dir && $dir$fileName" I hope will work now...
Thanks, much more flexible that hard coding the path. Just a mention, in the first example, if Chrome isn't your default browser Code Runner opens Chrome, but renders the file in your default browser leaving Chrome empty. The second example goes straight to your default browser. Great for me since I'm a Firefox user. Also, if filename has any spaces in it the above fails. Found this fix on gitbub; "html": "cd $dir && \"$fileName\""
Really depends on what/how it didn't work, lol. Of course there will be cases like that. But let me know what went wrong exactly, and I might be able to look into this!
@@ghosttogetherMy apologies I've been losing my mind trying to fix a live server launch browser error along with html not being recognised in VS Code. After 4 days of trying to find a tutorial I just came across a video of how to delete all settings and reset VS Studio to default settings
