Home/ Questions/Q 6118673
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-23T15:27:50+00:00

When I discovered that Node.js was built using the V8 JavaScript engine , I

  • 0

When I discovered that Node.js was built using the V8 JavaScript engine, I thought:

Great, web scraping will be easier as the page
will be rendered like in the browser, with a
“native” DOM supporting XPath and any AJAX calls on
the page executed.

  1. Why doesn’t it have a native DOM when it uses the same JavaScript engine as Chrome?
  2. Why doesn’t it have a mode to run JavaScript in retrieved pages?
  3. What am I not understanding about JavaScript engines vs the engine in a web browser?

Many thanks!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The DOM is the DOM, and the JavaScript implementation is simply a separate entity. The DOM represents a set of facilities that a web browser exposes to the JavaScript environment. There’s no requirement however that any particular JavaScript runtime will have any facilities exposed via the global object.

    What Node.js is is a stand-alone JavaScript environment completely independent of a web browser. There’s no intrinsic link between web browsers and JavaScript; the DOM is not part of the JavaScript language or specification or anything.

    I use the old Rhino Java-based JavaScript implementation in my Java-based web server. That environment also has nothing at all to do with any DOM. It’s my own application that’s responsible for populating the global object with facilities to do what I need it to be able to do, and it’s not a DOM.

    Note that there are projects like jsdom if you want a virtual DOM in your Node project. Because of its very nature as a server-side platform, a DOM is a facility that Node can do without and still make perfect sense for a wide variety of server applications. That’s not to say that a DOM might not be useful to some people, but it’s just not in the same category of services as things like process control, I/O, networking, database interop, and so on.

    There may be some “official” answer to the question “why?” out there, but it’s basically just the business of those who maintain Node (the Node Foundation now). If some intrepid developer out there decides that Node should ship by default with a set of modules to support a virtual DOM, and successfully works and works and makes that happen, then Node will have a DOM.

    • 0