Browser vs Node.js Runtime

Browser Runtime:

// Available in browser
window.alert('Hello');
document.getElementById('button');
localStorage.setItem('key', 'value');
fetch('https://api.example.com');

// NOT available in browser
const fs = require('fs'); // ERROR! 

 Node.js Runtime: 

// Available in Node.js
const fs = require('fs');
const http = require('http');
process.exit(0);

// NOT available in Node.js
window.alert('Hello'); // ERROR!
document.getElementById('button'); // ERROR! 

What Does "Providing a Runtime" Mean?

When we say "Node.js provides a runtime for JavaScript," we mean:

  1. It gives JavaScript a place to run outside the browser
  2. It provides access to system resources (files, network, processes)
  3. It manages memory and execution
  4. It handles errors and crashes
  5. It provides utility functions and modules

Real-World Example

When you run Playwright tests:

// Your test file: test.js
const { chromium } = require('playwright');

(async () => {
  const browser = await chromium.launch();
  const page = await browser.newPage();
  await page.goto('https://example.com');
  await browser.close();
})();

What happens when you run node test.js:

  1. Node.js runtime starts → Loads V8 engine, initializes event loop
  2. V8 parses your code → Converts JavaScript to machine instructions
  3. Node.js provides 'require' → Loads the Playwright module
  4. Event loop manages async operations → Browser launch, page navigation
  5. libuv handles I/O → Network requests, file system operations
  6. Process ends → Node.js cleans up and exits

Key Takeaway

Runtime environment = Everything needed to execute your code

Without Node.js runtime:

  • JavaScript would only run in browsers
  • No access to file system, network, or OS features
  • No way to build backend servers, CLI tools, or automation scripts

With Node.js runtime:

  • JavaScript can run anywhere
  • Full access to computer resources
  • Can build complete applications (frontend + backend)

The Node.js runtime is why tools like Playwright can control browsers, read files, make network requests, and automate complex workflows - all using JavaScript!

 

 

 

 

 

Comments

Post a Comment

Popular posts from this blog

Why do we need Node.js as a pre-requisite before installing Playwright?

Before we get into the details, let us first know the origin of Node.js Ryan Dahl created Node.js in 2009 . He was a software engineer frustrated with the limitations of existing web servers at the time. The Problem He Wanted to Solve In 2009, Ryan was working on web applications and noticed: Apache HTTP Server (the most popular web server) handled each connection with a separate thread This meant if you had 10,000 simultaneous users, you needed 10,000 threads Creating/managing so many threads consumed massive memory and CPU File upload progress bars were difficult - servers couldn't easily tell the browser "50% uploaded... 75% uploaded..." By combining JavaScript, V8, and non-blocking I/O, Ryan Dahl created a platform that revolutionized backend development and enabled JavaScript to dominate both frontend and backend.   Playwright is Built on Node.js Playwright is a Node.js Library Playwright is written in TypeScript/JavaScript and distributed as an npm package It r...
Read more

Await and Async

Typescript and Javascript is asynchronous . This means in our test which has multiple steps there is no guarantee that they will be executed one after the other. Let us consider an example where we typically try to login to a website.  Say, I want to book the book travel tickets. Below are the steps we follow manually.  Step1: Go to the Travel website URL  Step2: Provide Username and Password  Step3: Click on Login button to get into the application If we can notice, all these steps are sequential in nature. if we try to miss step2 and with out credentials clicking on Login button would not take us to the application.  Similarly, as we are trying to do automation ( web automation ), we should ensure all these steps are followed in sequence in above scenario. And we are relying on Typescript/Javascript to enable this automation. But we should understand that these are asynhronous. Meaning the steps can be executed in any order. So t...
Read more

What is spec.ts?

The spec file is a collection of test cases. Once we have done npm init playwright, we see a function @playwright/test imported. Using this test annotation, we can define the test cases. import {test} from '@playwright/test'; Test function is what we are importing. test('Name of the test case', 'callback function' { // playwright test steps // step 1 // step 2 ........ ........ ........ }); There are some built-in test sub-functions available that we can use with the test annotation. These help in controlling which tests to run or not. Example: test.only() -- Playwright will only run this test from the specs. test.skip() -- Playwright will not run this test from the specs. test.fail() -- Playwright will validate and check if the test is failing. if not, then it will complain.
Read more