If you want to know the specific latest version of a package available on the npm registry, run the following command: npm view versionįor example, here is how you can check the latest version of the Renovate package: Or, you can simply run the following command to check the available versions on the npm registry: npm view versions If you want to know the exact version of a package to install, you can simply search for it on the npm public registry database. If you want to install it globally, you can simply add the -g (short for –global) flag: npm install -g To Know Package Versions Available Here’s the command to run for npm install specific version: npm install above command will install the particular package version you want, alongside any packages that it depends on.įor example, to install a specific version of Renovate, you can run the following command: npm install you can use the shortened version of the command: npm i above command will install Renovate version 20.5.1 locally. You can simply specify the version using the syntax. In such cases, installing an exact package version could best suit your needs. However, what if the latest version causes some breaking changes to your application, or you just need a different version for any other reason? Renovate is a resourceful package that allows you to automate your dependency updates.
You can use the npm install command to download and install a package on your development environment.īy default, the npm install command fetches the latest available version of the specified package-in this case, it’s Renovate version 24.52.1, as of the time of this writing. Updating versions of Node.js packages manually? There’s an easier way How To Install A Specific Version Of A Package log( "CHILD: url received from parent process", url) Ĭonst browser = await puppeteer.7. The code snippet below is a simple example of running parallel downloads with Puppeteer.Ĭonst downloadPath = path. 💡 If you are not familiar with how child process work in Node I highly encourage you to give this article a read.
We can combine the child process module with our Puppeteer script and download files in parallel. Child process is how Node.js handles parallel programming. We can fork multiple child_proces in Node. Our CPU cores can run multiple processes at the same time. 💡 Learn more about the single threaded architecture of node here
Therefore if we have to download 10 files each 1 gigabyte in size and each requiring about 3 mins to download then with a single process we will have to wait for 10 x 3 = 30 minutes for the task to finish. It can only execute one process at a time.
You see Node.js in its core is a single-threaded system. However, if you have to download multiple large files things start to get complicated. In this next part, we will dive deep into some of the advanced concepts.
0 kommentar(er)
