Performance improvements and new features for Node.js: Competing with Deno and Bun
Many people are keen to discuss the speed of the new JavaScript runtime, which indirectly (and sometimes directly) implies that Node.js is slower or lacks certain integrated features. The development model of Deno 2 and Bun suggests that they are intended to be all-in-one toolkits for building JavaScript applications. They:
- Automatically load .env files
- Run the script in package.json
- Install package from npm
- Comes with built-in API for writing and running test suites
- Wait
Using Node.js requires the use of third-party tools to complete these tasks, such as using dotenv to load .env files.
However, Node.js has been catching up. This article will highlight three of the many features added since version 20 or 22. Let's get started.
Load .env file
Many people rely on dotenv to load environment files. We would write require('dotenv').config()
or import 'dotenv/config'
and then access the value from process.env
. Starting in version 20.6.0, you can use the --env-file
flag to specify the file from which Node.js should load environment variables.
For example, the following command will load environment variables from a .env file:
node --env-file=.env index.js
You can also load multiple files by passing the flag twice:
node --env-file=.env --env-file=config.env index.js
Some people have reported improvements in their application performance by removing the dotenv package and using Node.js directly. Here's what Wes Bos tweeted about his app startup time going from 1300ms to 1ms:
Monitor application files
I believe you have used different tools to monitor your source files and restart the application when you change the code. We have done this in various ways, one of which is using nodemon, a utility that monitors changes in source files and automatically restarts the server.
Starting with versions 18.11.0 and 16.19.0, the node
CLI gets two new flags for doing this: --watch
and --watch-path
. Running node --watch index.js
will start the application in watch mode and will watch the entry point and any required or imported modules. You should use the --watch-path
flag to specify the paths to monitor, rather than entry files and their imported modules.
There is also a flag related to watch mode: the --watch-preserve-output
flag. You can use this flag if you wish to prevent the console output from being cleared when the process is restarted in watch mode.
node --env-file=.env index.js
Run the script in package.json
While Node.js does not have a built-in package manager, most installations usually come bundled with npm. You've used npm run
or similar commands from various package managers to run scripts defined in package.json
. This isn't a problem, but Bun and Deno brag about the time it takes to get the package.json
script up and running, which may have made the Node team reconsider this option.
Starting with version 22.0.0, Node.js can now run scripts via the --run
flag, such as node --run dev
. This doesn't just replace npm run
without bringing any benefits or limitations. Using node --run
has been proven to be faster than the npm run
command. Some features intentionally excluded from other runtime implementations include:
- Run a pre-script or post-script in addition to the specified script.
- Define package manager specific environment variables.
You can read more about this flag in the documentation.
Summary
This article explores the latest improvements to Node.js that bring it closer to the integration capabilities provided by Deno 2 and Bun. We checked out the following features:
- Starting from version 20.6.0, use the
--env-file
flag to load .env files - Local file monitoring capabilities provided by the
--watch
and--watch-path
flags introduced in 18.11.0 and 16.19.0 versions - The
--run
flag, available since version 22.0.0, provides a faster way to runpackage.json
scripts
These updates help Node.js catch up with other runtimes by reducing the need for third-party tools and improving performance, security, and usability.
Original article published by me on Telerik blog
The above is the detailed content of ode.js Features You Didn't Know About. For more information, please follow other related articles on the PHP Chinese website!

The main difference between Python and JavaScript is the type system and application scenarios. 1. Python uses dynamic types, suitable for scientific computing and data analysis. 2. JavaScript adopts weak types and is widely used in front-end and full-stack development. The two have their own advantages in asynchronous programming and performance optimization, and should be decided according to project requirements when choosing.

Whether to choose Python or JavaScript depends on the project type: 1) Choose Python for data science and automation tasks; 2) Choose JavaScript for front-end and full-stack development. Python is favored for its powerful library in data processing and automation, while JavaScript is indispensable for its advantages in web interaction and full-stack development.

Python and JavaScript each have their own advantages, and the choice depends on project needs and personal preferences. 1. Python is easy to learn, with concise syntax, suitable for data science and back-end development, but has a slow execution speed. 2. JavaScript is everywhere in front-end development and has strong asynchronous programming capabilities. Node.js makes it suitable for full-stack development, but the syntax may be complex and error-prone.

JavaScriptisnotbuiltonCorC ;it'saninterpretedlanguagethatrunsonenginesoftenwritteninC .1)JavaScriptwasdesignedasalightweight,interpretedlanguageforwebbrowsers.2)EnginesevolvedfromsimpleinterpreterstoJITcompilers,typicallyinC ,improvingperformance.

JavaScript can be used for front-end and back-end development. The front-end enhances the user experience through DOM operations, and the back-end handles server tasks through Node.js. 1. Front-end example: Change the content of the web page text. 2. Backend example: Create a Node.js server.

Choosing Python or JavaScript should be based on career development, learning curve and ecosystem: 1) Career development: Python is suitable for data science and back-end development, while JavaScript is suitable for front-end and full-stack development. 2) Learning curve: Python syntax is concise and suitable for beginners; JavaScript syntax is flexible. 3) Ecosystem: Python has rich scientific computing libraries, and JavaScript has a powerful front-end framework.

The power of the JavaScript framework lies in simplifying development, improving user experience and application performance. When choosing a framework, consider: 1. Project size and complexity, 2. Team experience, 3. Ecosystem and community support.

Introduction I know you may find it strange, what exactly does JavaScript, C and browser have to do? They seem to be unrelated, but in fact, they play a very important role in modern web development. Today we will discuss the close connection between these three. Through this article, you will learn how JavaScript runs in the browser, the role of C in the browser engine, and how they work together to drive rendering and interaction of web pages. We all know the relationship between JavaScript and browser. JavaScript is the core language of front-end development. It runs directly in the browser, making web pages vivid and interesting. Have you ever wondered why JavaScr


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Dreamweaver Mac version
Visual web development tools

SAP NetWeaver Server Adapter for Eclipse
Integrate Eclipse with SAP NetWeaver application server.

SublimeText3 Chinese version
Chinese version, very easy to use

MantisBT
Mantis is an easy-to-deploy web-based defect tracking tool designed to aid in product defect tracking. It requires PHP, MySQL and a web server. Check out our demo and hosting services.

DVWA
Damn Vulnerable Web App (DVWA) is a PHP/MySQL web application that is very vulnerable. Its main goals are to be an aid for security professionals to test their skills and tools in a legal environment, to help web developers better understand the process of securing web applications, and to help teachers/students teach/learn in a classroom environment Web application security. The goal of DVWA is to practice some of the most common web vulnerabilities through a simple and straightforward interface, with varying degrees of difficulty. Please note that this software
