Complete Javascript: Zero To Expert

VS Code open karte hi ek hi cheez verify karni hoti hai: code run ho raha hai ya nahi. This section shows how to set up VS Code, run your first JavaScript using console.log, and understand the difference between running JS in the browser vs Node.js - so you don’t get stuck when APIs behave differently.

Overview

This section covers (1) installing and configuring VS Code for JavaScript, (2) running a minimal JS file that prints using console.log, and (3) learning comments plus the browser vs Node runtime differences. Use it when you want a working local environment and a correct mental model for where your code executes.

Quick Reference

Parameters

console.log

Comments (no runtime parameters)

Browser vs Node: “parameters” that affect availability

Code Example

// first-run.js
// This file runs in Node.js (terminal). Browser usage is shown later.

console.log("JS is running in Node");

// Comments examples:
const user = {
  name: "Riya",
  // Single-line comment inside an object
  age: 19
};

/*
Block comment:
Use it for longer notes about why something exists.
*/

console.log(user);
console.log(user.name, user.age);

  
    
      // Browser console output:
      console.log("JS is running in the browser");

      // Block comment example:
      /*
        In the browser, APIs like window/document are available.
      */
    
  

First-Run Checklist (framework):

• Install VS Code
• Install Node.js (so `node` command works)
• Create `first-run.js`
• Open VS Code terminal: `node first-run.js`
• Open DevTools Console (browser) and verify the HTML example prints too

Response Format

Expected output (Node)

{
  "environment": "node",
  "logs": [
    "JS is running in Node",
    { "name": "Riya", "age": 19 },
    "Riya",
    19
  ]
}

Expected output (Browser)

{
  "environment": "browser",
  "logs": [
    "JS is running in the browser"
  ]
}

Field notes:

• environment: where the JS executed (`node` or `browser`)
• logs: values passed to `console.log` in execution order

Notes & Best Practices

• console.log is not the same everywhere: Node prints to terminal; browser prints to DevTools Console.
• Environment-specific APIs: `window/document` are browser globals; `fs/process` are Node globals. If you call the wrong one, you’ll get `ReferenceError`.
• Error handling: if the file doesn’t run, check `node yourfile.js` command path and filename spelling in VS Code terminal.
• Comments affect readability only: comments don’t change execution; keep them precise (“what/why”), not “what the code already shows”.

This setup is the base for everything next: once you know where your JS runs and how `console.log` surfaces output, debugging and API usage become predictable across browser and Node runtimes.

Chapter 1 complete. Next chapter likhu ya koi change chahiye?