![\"next\"](\"//images.ctfassets.net/hspc7zpa5cvq/5gcP7k5WIw7h4mSYuZIDMq/898ad62724d65c969e60d305e1e85d2e/next.png\")
In my previous blog post, I explored the differences, advantages, and disadvantages of three of the most popular Node.js frameworks: Express, Koa, and Hapi. In this blog post, I’m going to examine the differences between three more very popular frameworks: Next, Nuxt, and Nest. These three frameworks are server-side rendering, and they are closely related to React, Vue, and Angular (the three most widely used front-end frameworks), respectively.
\nThe comparison is based on:
\nNext is the most popular framework compared to the other two. It has more npm weekly downloads, GitHub stars and number of contributors.
\nNext.js is a React framework that lets you build server-side rendering and static web applications using React.
\nInstall it:
\nnpm install --save next react react-dom\nand add a script to your package.json like this:
\n{\n \"scripts\": {\n \"dev\": \"next\",\n \"build\": \"next build\",\n \"start\": \"next start\"\n }\n}\nAfter that, the file-system is the main API. Every .js file becomes a route that gets automatically processed and rendered.
\nPopulate ./pages/index.js inside your project:
function Home() {\n return <div>Hello world!</div>;\n}\n\nexport default Home;\nThen just run npm run dev and go to http://localhost:3000. To use another port, you can run npm run dev -- -p <your port here>.
To measure the performance, I used Apache Bench for benchmarking, which highlights how many requests per second the app is capable of serving. I also used lighthouse to audit performance, accessibility, best practices, and SEO.
\n
This is a basic Hello World app in Next.js. It handles 550.87 requests per second. This value is the result of dividing the number of requests by the total time taken. The average time spent per request is 18.153 ms.
\nCompared to the other two frameworks, Next.js scored better overall than Nuxt.js but worse than Nest.js
\n![\"next1\"](\"//images.ctfassets.net/hspc7zpa5cvq/6SWp0mED1Nb9fXIBM7WwXC/4982654aa94d5d89fc6a0053b1ed90d1/next1.png\")
In the report provided by lighthouse, we can see that the performance, accessibility, best practices, and SEO scores are all above 70, which is good, but compared with the other two frameworks, it had the lowest score for Performance and has the highest score in Best Practices.
\nThe Next.js community communicates through chat, slack, issues and pull request on GitHub.
\nAlso, in the repo awesome-nextjs, there is a list of essentials, articles, boilerplates, extensions, apps, books, and videos that are useful for developers using Next.js
\nNuxt is a Vue.js Meta Framework to create complex, fast, and universal web applications quickly.
\nInstall it:
\n$ npm i nuxt\nTo create a basic app:
\n$ npx create-nuxt-app <project-name>\nYou can start directly with the CLI create-nuxt-app for the latest updates.\nOr you can start by using one of the starter templates:\nstarter: Basic Nuxt.js project template\nexpress: Nuxt.js + Express\nkoa: Nuxt.js + Koa\nadonuxt: Nuxt.js + AdonisJS\nmicro: Nuxt.js + Micro\nnuxtent: Nuxt.js + Nuxtent module for content heavy sites
\nThis is the most basic example of a “Hello World!” app on Nuxt:
\n<template>\n <div>\n <h1>Hello world!</h1>\n <NLink to=\"/about\">\n About Page\n </NLink>\n </div>\n</template>\n\n<script>\nexport default {\n head: {\n title: 'Home page'\n }\n}\n</script>\nthis.items[key]=value or adding a new data property. ![\"nuxt\"](\"//images.ctfassets.net/hspc7zpa5cvq/77aAB8VVmQi8Kif9gTCQ4U/2fd522c337487dce659994e37e8edbeb/nuxt.png\")
This is a basic Hello World app in Nuxt.js. It handles 190.05 requests per second. The average time spent per request is 52.619 ms. On this metric, Nuxt.js performs the worst compared to the other two frameworks.
\n![\"nuxt1\"](\"//images.ctfassets.net/hspc7zpa5cvq/7hS5nyqzb8UAFd9NidP5sQ/e0cf7d7936142535c0c8aedaad038d81/nuxt1.png\")
Nuxt.js has the highest score in three of the four measures; performance, accesibility and SEO.
\nThere is a GitHub organization where you can find modules and projects from the Nuxt.js community. There is also a curated list of awesome things related to Nuxt.js awesome-nuxt including Modules, tools, mention of Nuxt.js, showcase, tutorials, blogs, books, starter template, official examples, and projects using Nuxt.js.
\nThe community communicates through Gitter Chat Room, Telegram, Russian community, Discord, Twitter and YouTube Channel
\nA progressive Node.js framework for building efficient, scalable, and enterprise-grade server-side applications on top of TypeScript and JavaScript (ES6, ES7, ES8), Nest is heavily inspired by Angular.
\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).
\nUnder the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like e.g. Fastify, allowing for easy use of the myriad third-party plugins which are available.
\nInstall it:
\n$ npm i @nestjs/cli\n$ nest new project-name\nAlternatively, to install the TypeScript starter project with Git:
\n$ git clone https://github.com/nestjs/typescript-starter.git project\n$ cd project\n$ npm install\n$ npm run start\nAfter installing Nest.js with the npm cli command, and creating a new project with nest new project-name, a src/ directory will be created and populated with several core files, including main.ts.\nThe main.ts includes an async function, which will bootstrap our application:
import { NestFactory } from '@nestjs/core';\nimport { ApplicationModule } from './app.module';\n\nasync function bootstrap() {\n const app = await NestFactory.create(ApplicationModule);\n await app.listen(3000);\n}\nbootstrap();\nAnd then to run the app that listens on port 3000, you execute:
\n$ npm run start\n![\"nest\"](\"//images.ctfassets.net/hspc7zpa5cvq/1I29Vhrd0whIOGhQsGPMUT/8092e2e37a828c4cad9f70628854f378/nest.png\")
This is a basic Hello World app in Nest.js. It handles 928.18 requests per second. The average time spent per request is 10.774 ms. On this metric, Nest.js performed the best out of the three frameworks we compared.
\n![\"nest2\"](\"//images.ctfassets.net/hspc7zpa5cvq/4bL41CK2YoIadG76nKqbgp/a4dd5d419adfee21dbfa09d8b7088c61/nest2.png\")
In the report provided by lighthouse, Nest.js has a very high performance, but scored comparatively lower on other key factors:accessibility, best practices and SEO.
\nThere is a group of developers providing handy packages on NestJS Community organization GitHub. Some of their popular packages are: nestjs-config, a config module for NestJS using dotenv. nest-access-control, Role and Attribute-based access control for NestJS and nestjs-flub, pretty error stack viewer.
Even if Nest is not the most popular framework, is the one that has the better performance and has many advantages. You should give it a try!
\nThe community has a spectrum chat and Twitter
"}}},{"slug":"understanding-streams-in-node-js","title":"Understanding Streams in Node.js","createdAt":"May 30, 2020","author":{"name":"Liz Parody"},"image":{"file":{"url":"//images.ctfassets.net/xmu5vdhtphau/iF3PJ65DN4RZh7hUSRU5X/055bb44f2ab60b4efcea179638f68efe/21-min.jpg","fileName":"21-min.jpg"}},"bodyContent":{"childMarkdownRemark":{"html":"Streams in Node.js have a reputation for being hard to work with, and even harder to understand.
\nIn the words of Dominic Tarr: “Streams are Node’s best and most misunderstood idea.” Even Dan Abramov, creator of Redux and core team member of React.js is afraid of Node streams.
\nThis article will help you understand streams and how to work with them. So, don’t be afraid. We can figure this out!
\nStreams are one of the fundamental concepts that power Node.js applications. They are data-handling method and are used to read or write input into output sequentially.
\nStreams are a way to handle reading/writing files, network communications, or any kind of end-to-end information exchange in an efficient way.
\nWhat makes streams unique, is that instead of a program reading a file into memory all at once like in the traditional way, streams read chunks of data piece by piece, processing its content without keeping it all in memory.
\nThis makes streams really powerful when working with large amounts of data, for example, a file size can be larger than your free memory space, making it impossible to read the whole file into the memory in order to process it. That’s where streams come to the rescue!
\nUsing streams to process smaller chunks of data, makes it possible to read larger files.
\nLet’s take a “streaming” services such as YouTube or Netflix for example: these services don’t make you download the video and audio feed all at once. Instead, your browser receives the video as a continuous flow of chunks, allowing the recipients to start watching and/or listening almost immediately.
\nHowever, streams are not only about working with media or big data. They also give us the power of ‘composability’ in our code. Designing with composability in mind means several components can be combined in a certain way to produce the same type of result. In Node.js it’s possible to compose powerful pieces of code by piping data to and from other smaller pieces of code, using streams.
\nStreams basically provide two major advantages compared to other data handling methods:
\nfs.createWriteStream() lets us write data to a file using streams.fs.createReadStream() lets us read the contents of a file.net.SocketIf you have already worked with Node.js, you may have come across streams. For example, in a Node.js based HTTP server, request is a readable stream and response is a writable stream. You might have used the fs module, which lets you work with both readable and writable file streams. Whenever you’re using Express you are using streams to interact with the client, also, streams are being used in every database connection driver that you can work with, because of TCP sockets, TLS stack and other connections are all based on Node.js streams.
We first require the Readable stream, and we initialize it.
\nconst Stream = require('stream')\nconst readableStream = new Stream.Readable()\nNow that the stream is initialized, we can send data to it:
\nreadableStream.push('ping!')\nreadableStream.push('pong!')\nIt’s highly recommended to use async iterator when working with streams. According to Dr. Axel Rauschmayer, Asynchronous iteration is a protocol for retrieving the contents of a data container asynchronously (meaning the current “task” may be paused before retrieving an item). Also, it’s important to mention that the stream async iterator implementation use the ‘readable’ event inside.
\nYou can use async iterator when reading from readable streams:
\nimport * as fs from 'fs';\n\nasync function logChunks(readable) {\n for await (const chunk of readable) {\n console.log(chunk);\n }\n}\n\nconst readable = fs.createReadStream(\n 'tmp/test.txt', {encoding: 'utf8'});\nlogChunks(readable);\n\n// Output:\n// 'This is a test!\\n'\nIt’s also possible to collect the contents of a readable stream in a string:
\nimport {Readable} from 'stream';\n\nasync function readableToString2(readable) {\n let result = '';\n for await (const chunk of readable) {\n result += chunk;\n }\n return result;\n}\n\nconst readable = Readable.from('Good morning!', {encoding: 'utf8'});\nassert.equal(await readableToString2(readable), 'Good morning!');\nNote that, in this case, we had to use an async function because we wanted to return a Promise.
\nIt’s important to keep in mind to not mix async functions with EventEmitter because currently, there is no way to catch a rejection when it is emitted within an event handler, causing hard to track bugs and memory leaks. The best current practice is to always wrap the content of an async function in a try/catch block and handle errors, but this is error prone. This pull request aims to solve this issue once it lands on Node core.
To learn more about Node.js streams via async iteration, check out this great article.
\nstream.Readable.from(iterable, [options]) it’s a utility method for creating Readable Streams out of iterators, which holds the data contained in iterable. Iterable can be a synchronous iterable or an asynchronous iterable. The parameter options is optional and can, among other things, be used to specify a text encoding.
const { Readable } = require('stream');\n\nasync function * generate() {\n yield 'hello';\n yield 'streams';\n}\n\nconst readable = Readable.from(generate());\n\nreadable.on('data', (chunk) => {\n console.log(chunk);\n});\nAccording to Streams API, readable streams effectively operate in one of two modes: flowing and paused. A Readable stream can be in object mode or not, regardless of whether it is in flowing mode or paused mode.
\nstream.read() method must be called explicitly to read chunks of data from the stream.In a flowing mode, to read data from a stream, it’s possible to listen to data event and attach a callback. When a chunk of data is available, the readable stream emits a data event and your callback executes. Take a look at the following snippet:
\nvar fs = require(\"fs\");\nvar data = '';\n\nvar readerStream = fs.createReadStream('file.txt'); //Create a readable stream\n\nreaderStream.setEncoding('UTF8'); // Set the encoding to be utf8. \n\n// Handle stream events --> data, end, and error\nreaderStream.on('data', function(chunk) {\n data += chunk;\n});\n\nreaderStream.on('end',function() {\n console.log(data);\n});\n\nreaderStream.on('error', function(err) {\n console.log(err.stack);\n});\n\nconsole.log(\"Program Ended\");\nThe function call fs.createReadStream() gives you a readable stream. Initially, the stream is in a static state. As soon as you listen to data event and attach a callback it starts flowing. After that, chunks of data are read and passed to your callback. The stream implementor decides how often a data event is emitted. For example, an HTTP request may emit a data event once every few KBs of data are read. When you are reading data from a file you may decide you emit a data event once a line is read.
When there is no more data to read (end is reached), the stream emits an end event. In the above snippet, we listen to this event to get notified when the end is reached.
\nAlso, if there is an error, the stream will emit and notify the error.
\nIn paused mode, you just need to call read() on the stream instance repeatedly until every chunk of data has been read, like in the following example:
\nvar fs = require('fs');\nvar readableStream = fs.createReadStream('file.txt');\nvar data = '';\nvar chunk;\n\nreadableStream.on('readable', function() {\n while ((chunk=readableStream.read()) != null) {\n data += chunk;\n }\n});\n\nreadableStream.on('end', function() {\n console.log(data)\n});\nThe read() function reads some data from the internal buffer and returns it. When there is nothing to read, it returns null. So, in the while loop, we check for null and terminate the loop. Note that the readable event is emitted when a chunk of data can be read from the stream.
\nAll Readable streams begin in paused mode but can be switched to flowing mode in one of the following ways:
stream.resume() method.stream.pipe() method to send the data to a Writable.The Readable can switch back to paused mode using one of the following:
stream.pause() method.stream.unpipe() method.The important concept to remember is that a Readable will not generate data until a mechanism for either consuming or ignoring that data is provided. If the consuming mechanism is disabled or taken away, the Readable will attempt to stop generating the data.\nAdding a readable event handler automatically make the stream to stop flowing, and the data to be consumed via readable.read(). If the 'readable' event handler is removed, then the stream will start flowing again if there is a 'data' event handler.
To write data to a writable stream you need to call write() on the stream instance. Like in the following example:
var fs = require('fs');\nvar readableStream = fs.createReadStream('file1.txt');\nvar writableStream = fs.createWriteStream('file2.txt');\n\nreadableStream.setEncoding('utf8');\n\nreadableStream.on('data', function(chunk) {\n writableStream.write(chunk);\n});\nThe above code is straightforward. It simply reads chunks of data from an input stream and writes to the destination using write(). This function returns a boolean value indicating if the operation was successful. If true, then the write was successful and you can keep writing more data. If false is returned, it means something went wrong and you can’t write anything at the moment. The writable stream will let you know when you can start writing more data by emitting a drain event.
Calling the writable.end() method signals that no more data will be written to the Writable. If provided, the optional callback function is attached as a listener for the 'finish' event.
// Write 'hello, ' and then end with 'world!'.\nconst fs = require('fs');\nconst file = fs.createWriteStream('example.txt');\nfile.write('hello, ');\nfile.end('world!');\n// Writing more now is not allowed!\nUsing a writable stream you can read data from a readable stream:
\nconst Stream = require('stream')\n\nconst readableStream = new Stream.Readable()\nconst writableStream = new Stream.Writable()\n\nwritableStream._write = (chunk, encoding, next) => {\n console.log(chunk.toString())\n next()\n}\n\nreadableStream.pipe(writableStream)\n\nreadableStream.push('ping!')\nreadableStream.push('pong!')\n\nwritableStream.end()\nYou can also use async iterators to write to a writable stream, which is recommended
\nimport * as util from 'util';\nimport * as stream from 'stream';\nimport * as fs from 'fs';\nimport {once} from 'events';\n\nconst finished = util.promisify(stream.finished); // (A)\n\nasync function writeIterableToFile(iterable, filePath) {\n const writable = fs.createWriteStream(filePath, {encoding: 'utf8'});\n for await (const chunk of iterable) {\n if (!writable.write(chunk)) { // (B)\n // Handle backpressure\n await once(writable, 'drain');\n }\n }\n writable.end(); // (C)\n // Wait until done. Throws if there are errors.\n await finished(writable);\n}\n\nawait writeIterableToFile(\n ['One', ' line of text.\\n'], 'tmp/log.txt');\nassert.equal(\n fs.readFileSync('tmp/log.txt', {encoding: 'utf8'}),\n 'One line of text.\\n');\nThe default version of stream.finished() is callback-based but can be turned into a Promise-based version via util.promisify() (line A).
\nIn this example, it is used the following two patterns:
\nWriting to a writable stream while handling backpressure (line B):
\nif (!writable.write(chunk)) {\n await once(writable, 'drain');\n}\nClosing a writable stream and waiting until writing is done (line C):
\nwritable.end();\nawait finished(writable);\nPiping is a mechanism where we provide the output of one stream as the input to another stream. It is normally used to get data from one stream and to pass the output of that stream to another stream. There is no limit on piping operations. In other words, piping is used to process streamed data in multiple steps.
\nIn Node 10.x was introduced stream.pipeline(). This is a module method to pipe between streams forwarding errors and properly cleaning up and provide a callback when the pipeline is complete.
Here is an example of using pipeline:
\nconst { pipeline } = require('stream');\nconst fs = require('fs');\nconst zlib = require('zlib');\n\n// Use the pipeline API to easily pipe a series of streams\n// together and get notified when the pipeline is fully done.\n// A pipeline to gzip a potentially huge video file efficiently:\n\npipeline(\n fs.createReadStream('The.Matrix.1080p.mkv'),\n zlib.createGzip(),\n fs.createWriteStream('The.Matrix.1080p.mkv.gz'),\n (err) => {\n if (err) {\n console.error('Pipeline failed', err);\n } else {\n console.log('Pipeline succeeded');\n }\n }\n);\npipeline should be used instead of pipe, as pipe is unsafe.
The Node.js stream module provides the foundation upon which all streaming APIs are build.
\nThe Stream module is a native module that shipped by default in Node.js. The Stream is an instance of the EventEmitter class which handles events asynchronously in Node. Because of this, streams are inherently event-based.
\nTo access the stream module:
\nconst stream = require('stream');\nThe stream module is useful for creating new types of stream instances. It is usually not necessary to use the stream module to consume streams.
Due to their advantages, many Node.js core modules provide native stream handling capabilities, most notably:
\nnet.Socket is the main node api that is stream are based on, which underlies most of the following APIsprocess.stdin returns a stream connected to stdinprocess.stdout returns a stream connected to stdoutprocess.stderr returns a stream connected to stderrfs.createReadStream() creates a readable stream to a filefs.createWriteStream() creates a writable stream to a filenet.connect() initiates a stream-based connectionhttp.request() returns an instance of the http.ClientRequest class, which is a writable streamzlib.createGzip() compress data using gzip (a compression algorithm) into a streamzlib.createGunzip() decompress a gzip stream.zlib.createDeflate() compress data using deflate (a compression algorithm) into a streamzlib.createInflate() decompress a deflate stream![\"cheat1\"](\"//images.ctfassets.net/hspc7zpa5cvq/3s8p9qQe6zDEfhwLyq5fQR/7ce28dd384a590009aaaa16886bb83eb/cheat1.png\")
![\"cheat2\"](\"//images.ctfassets.net/hspc7zpa5cvq/1vZrS7rb7U7DRb5TtT8hs8/bb6285794d4141c3a572770651fcc753/cheat2.png\")
\n![\"cheat3\"](\"//images.ctfassets.net/hspc7zpa5cvq/2rPAh1mmsLg02i0hLBG2DG/9829c1fb9cf396d952f1d155ce799f13/cheat3.png\")
\n![\"cheat3\"](\"//images.ctfassets.net/hspc7zpa5cvq/3HncUkiyjekdWjN8MwQbfi/29b3ad1806e8ce161a889c76667e780f/cheat3.png\")
Here are some important events related to writable streams:
\nerror – Emitted to indicate that an error has occurred while writing/piping.pipeline – When a readable stream is piped into a writable stream, this event is emitted by the writable stream.unpipe – Emitted when you call unpipe on the readable stream and stop it from piping into the destination stream.This was all about the basics of streams. Streams, pipes, and chaining are the core and most powerful features in Node.js. Streams can indeed help you write neat and performant code to perform I/O.
\nAlso, there is a Node.js strategic initiative worth looking to, called BOB, aiming to improve Node.js streaming data interfaces, both within Node.js core internally, and hopefully also as future public APIs.
\nSpecial thanks to Matteo Colina and Jeremiah Senkpiel for your feedback!
\nThis article was first published in NodeSource blog on January 2017.
\nAs with any programming language, platform, or tool, the first step to using it is getting it installed. Many of them typically come with a speedy way to upgrade when a new version is available.
\nBy default, there's not a way to upgrade the version of Node.js you've got from within Node.js itself. That said, there's a fantastic tool for the community called nvm that allows you to manage the versions of Node.js that you've got installed locally.
\nOne awesome aspect of nvm is that it manages the versions of Node.js, it doesn't just upgrade them. This means you can have the latest version of Node.js, the latest versions of all the LTS release lines, and any number of other versions you want to use or test as well.
In this quick tutorial, we'll take a look at how to install nvm, and then how to start using it as your version manager for Node.js. Once we've completed the tutorial, you'll be ready to take the next step with Node.js.
\nThis guide covers installing nvm on macOS and Linux - note that all versions of Node.js may not support every version of macOS or Linux.
\nHere's the abbreviated guide, highlighting the major steps:
\nDownload the nvm install script via cURL:
\ncurl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.0/install.sh | bashnvm --version, which should return the version of nvm installed.Install the version of Node.js you want
\nnvm install nodenvm use nodenvm install --ltsnvm use --ltsIn some cases, like when installing Node.js releases from their source or installing versions of Node.js before 0.8.6 (when the project started shipping binaries), you'll need to ensure that your system has the appropriate C++ build tools.
For LTS and modern releases, you will not need this step. That said, it's a nice to have to ensure that the majority of requirements are met in any scenario.
\nOn macOS, you've got two options for a C++ compiler: the full XCode application or the stand-alone Command Line Tools portion of Xcode.
\nTo get these on macOS, you can follow these steps:
\nRun xcode-select --install as a command
InstallOn Linux, the C++ compiler will vary from distribution to distribution. For example, on Debian and Ubuntu, you'll need to install build-tools and libssl-dev, but this may be different on your given Linux distribution.
To get build-tools and libssl-dev on Debuan and Ubuntu distributions, you can run these commands:
sudo apt-get install build-essential # Install the build-essential package - let this run to completion\n\nsudo apt-get install libssl-dev # Install the libssl-dev package - also let this one run to completion\nOnce you've got the right C++ compiler for your system, now it's time to run the nvm install script. Here are the single-step install scripts for both macOS and Linux. You've got the option of cURL or Wget but both achieve the same result.
\nNote: If your Linux system doesn't have either cURL or Wget, you can run sudo apt-get install curl and use the cURL method.
To install nvm with the cURL method, run the following command in your terminal:
\ncurl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.0/install.sh | bash\nTo install nvm with the Wget method, run the following command in your terminal:
\nwget -qO- https://raw.githubusercontent.com/creationix/nvm/v0.33.0/install.sh | bash\nAfter running the install script from Step 2, nvm should have successfully installed. To ensure that nvm is up and running on your machine, you can test it with the following command:
\nnvm --version\nThis command will return something like (though not necessarily exactly) the following:
\nnvm --version # The command we ran - it checks the currently installed version of nvm\n0.33.0 # The current version of nvm - yours may differ!\nnvm command after running the install script?If you're using macOS, you may be missing a .bash_profile file - to troubleshoot this, you can run touch ~/.bash_profile in your command line and re-run the installer script.
If the problem persists after that, you can open the existing .bash_profile file (using your favorite text editor) and add the following line to it:
source ~/.bashrc\nIf you're still having issues, you can take a peek at this issue to find a discussion of the problem and a collection of possible resolutions.
\nCongratulations! You've now got nvm - a tool to easily allow you to manage and swap out the versions of Node.js you've got installed locally. Now, let's get you started with doing just that.
To install the latest available version of Node.js, you can use the following command:
\nnvm install node\nNext, to use that version of Node.js in any new shell, you can simply run the use command:
nvm use node\nTo install the latest available LTS version of Node.js, you can run the following command:
\nnvm install --lts\nAnd to use that latatestTS version of Node.js in any new shell, you can simply run the use command:
nvm use --lts\nNow you've got a fantastic version manager for Node.js. It's time to start building!
\nWe've got some resources to get you kickstarted! Both the breadth and depth of the Node.js and the JavaScript ecosystems are quite large - in addition to the developer tools like NodeSource N|Solid and Certified Modules, we've got a ton of tutorials, guides, and articles to help you get kick started with Node.js.
\nIf you're interested in keeping your code clean, maintainable, and collaborative, take a peek at our post on using ESLint for linting your JavaScript applications. Are you interested in building web applications with Node.js? One of the most challenging aspects of web apps is security - you can learn security best practices for Express to lock down your web apps, to prevent breaches and attacks. Or, maybe you want to deploy your Node.js apps with Docker? Then you should definitely read our article on dockerizing your Node.js applications.
\nThat said, if you want to keep in touch with the Node.js ecosystem, you should follow @NodeSource on Twitter! We'll keep you updated with important news from the core Node.js project, fresh and useful Node.js tutorials, and more.
"}}}],"videos":[{"slug":"need-to-node-volume-66","title":"Need to Node – Volume 66","image":{"file":{"url":"//images.ctfassets.net/xmu5vdhtphau/47M1ZCRvNDb4uYnCpN89QG/ec93803c06da2a34b1bc40514c107497/3-min.png","fileName":"3-min.png"}},"bodyContent":{"childMarkdownRemark":{"html":"In this volume of Need to Node, you can find the latest news on Node.js’s version 14 Release, Diagnostics in Node.js and The Cost of JavaScript Frameworks
\nNeed to Node is a weekly bulletin designed to keep you up-to-date with the latest news on the Node.js project, events and articles. You are always welcome to collaborate and participate. Please let us know if we missed a piece of content you think should be included!
\nNode.js version 14 Released — Woo-hoo it’s finally here! Node.js v.14 now becomes the current release line with it becoming a LTS (Long Term Support) release in October. It’s recommended to keep using Node.js version 12 for now. Some of the most exciting features include:
\nThe Cost of JavaScript Frameworks. With JavaScript you end up paying a performance tax no less than four times:
\nIf you find any Node.js or JavaScript related content over the next week (or beyond!), never hesitate to reach out to us on Twitter at @NodeSource to share and get it included in Need to Node - our DMs are open if you don’t want to share publicly!
"}}},{"slug":"new-features-nodejs-version-14","title":"New and Exciting Features to Land in Node.js Version 14","image":{"file":{"url":"//images.ctfassets.net/xmu5vdhtphau/4HIwVhFjrKrBmds10NlfeW/4193d762cccd04afeef8b9baba8ce772/1-min.png","fileName":"1-min.png"}},"bodyContent":{"childMarkdownRemark":{"html":"Node.js 14 has just been released. It comes with full of new features and enhancements. More importantly, it will be promoted to Long-Term Support in October, so now it's the moment to start testing our applications and try the new features to ensure a smooth transition.
\nIn this webinar we will be showing the most relevant of these new features.
"}}},{"slug":"need-to-node-volume-64","title":"Need to Node – Volume 64","image":{"file":{"url":"//images.ctfassets.net/xmu5vdhtphau/4pkqP0mjoj4FuZpgYCTicI/06b9039051055aefb5796f9ee82a5e66/2-min.png","fileName":"2-min.png"}},"bodyContent":{"childMarkdownRemark":{"html":"In this volume of Need to Node, you can find the latest news on the Node.js v13.11.0 (Current) Release, npm is joining GitHub and Three Things You Didn't Know You Could Do with npm Scripts.
\nNeed to Node is a weekly bulletin designed to keep you up to date with the latest news on the Node.js project, events and awesome articles. You are always welcome to collaborate and participate. Please let us know if we missed a piece of content you think should be included!
\nasync_hooks, cli and fs.^, >=, or * required. Exciting! By Valeri Karpov If you find any Node.js or JavaScript related content over the next week (or beyond!), never hesitate to reach out to us on Twitter at @NodeSource to share and get it included in Need to Node - our DMs are open if you don’t want to share publicly!
"}}}]},"allContentfulPost":{"edges":[{"node":{"slug":"meet-anna-henningsen-core-contributor-and-engineer","title":"Meet Anna Henningsen - Core Contributor & Engineer","headLine":"What keeps me motivated to work on Node.js is the community and the technological challenge. Having the opportunity to improve the developer experience for thousands, maybe millions of people, that’s a very unique thing, and I think it is worth a lot.","avatar":{"file":{"url":"//images.ctfassets.net/xmu5vdhtphau/2ewVjWlpCbAxvJ9XuGFot8/bad24efcea89a8ef5b61053883b17e73/anna.jpg","fileName":"anna.jpg"}}}},{"node":{"slug":"meet-adrian-estrada-vp-of-engineering-nodesource","title":"Meet Adrian Estrada - VP of Engineering @ NodeSource","headLine":"It was definitely about creating opportunities for others. I know I can do something to help and provide opportunities to people so I do what I can to transform the city. ","avatar":{"file":{"url":"//images.ctfassets.net/xmu5vdhtphau/5oi3ODySdvXsDHM6Xv33aa/ae6683cc99c4bc09774ba85add0b9d34/adri.jpeg","fileName":"adri.jpeg"}}}},{"node":{"slug":"meet-trevor-norris-core-contributor-and-engineer-nodesource","title":"Meet Trevor Norris - Core Contributor & Engineer @ NodeSource","headLine":"One of the best things about working in open source is that you get to work on what you find most interesting. It is easy to stay involved in open source because you can pick and choose what you want to work on. But it's not always easy.","avatar":{"file":{"url":"//images.ctfassets.net/xmu5vdhtphau/61I48ZBFi43Wp3FIaGk6Js/f198079b401c1a004f6b4a40bd0c0f8c/tnorris.jpeg","fileName":"tnorris.jpeg"}}}}]}},"pageContext":{}}}