Skip to main content

JavaScript Runtime Environment

 What is a Runtime Environment?

A runtime environment is where your program will be executed. It determines what global objects your program can access and it can also impact how it runs.

How does the JavaScript Environment Work?

The JavaScript runtime environment provides access to built-in libraries and objects that are available to program so that it can interact with the outside world and make the code work.

Different browsers have different JavaScript Runtime Environments.

In the context of a browser, JS runtime  is comprised of the following elements:

  • The JavaScript Engine
  • Web APIs
  • The Call Back Queue
  • The Event Loop
Javascript-runtimeimg

The JavaScript Engine

All the browsers have a JavaScript Engine. But all are not necessarily the same engine. Also, all the engines follow the same standard although their implementation is different.

For example, Google Chrome has the V8 engine and Mozilla Firefox has Spyder Monkey as a JavaScript engine.

The JavaScript Engine parses the code for us. It has two major components:

  • Memory Heap 
  • Call Stack

Memory Heap

A memory heap is a section of unstructured memory that is used for the allocation of objects and variables.

Call Stack

The call stack keeps the track of where we are in the program and runs in a last-in, first-out way.

Web APIs

There are a large number of APIs available in web browsers that allow us to do a wide variety of operations like DOM manipulation, Fetch APIs, Drawing graphics, etc., all these types of operations are carried out on Web APIs.

Callback Queue

The callback queue stores the callback functions sent from the Web APIs in the order in which they are added.

Event Loop

The job of the event loop is to constantly monitor the state of the call stack and the call back queue. If the call stack is empty, it will grab a callback from the callback queue and put it onto the call stack, scheduling it for execution.

Comments

Popular posts from this blog

JavaScript Scopes

 What is a variable scope? The visibility and accessibility of a variable is determined by its scope. JavaScript has three scopes: Global scope Local scope and Block scope Global Scope A variable that can be accessible everywhere in the script.  Local Scope    If you declare a variable inside a function are local to the function. They are called local variables. Output:  I am from say I am from global Scope Chain If interpreter cannot find a variable in its local context, then it looks for it in parent contexts until it's found. This is called scope chain. Output:  Hello I am message In the above script, the JavaScript performs the following: It looks up for the variable message in the current context (Functional Execution Context) of the say(). But it cannot find it. So it goes out of the function and looks in the outer execution context which is the global execution context. It found the message variable there. The way that JavaScript resolves a variable is by looking at in its c

JavaScript Hoisting

 Hoisting JavaScript Hoisting refers to the process where the interpreter allocates memory for variables and function declarations prior to the execution of the code. Declarations that are made using the var keyword are initialized with the default value of undefined Declarations made using the let and the const keywords are not initialized as a part of the hoisting  Hoisting takes place during the creation phase of the Execution Context. consider the following script:  output: undefined Steps involved in the execution of the above script: A new Global Execution Context is created. num variable is initialized with undefined . In the execution phase, the code is executed line-by-line. In the first line it logs undefined to the console. Line two is skipped as it already defined num in the creation phase. In line three a value of 6 is assigned to num. let and const keywords let and const keywords are hoisted but not initialized Consider the following script:  output: ReferenceError: