DEV Community: Ruy Adorno

Node.js v19.2.0 Release

Ruy Adorno — Tue, 29 Nov 2022 20:08:38 +0000

A new version of the Node.js runtime is out now! 🥳

Notable changes:

buffer:

add new File class

deps:

update timezone
update V8 to 10.8.168.20

doc:

deprecate use of invalid ports in url.parse

util:

add fast path for utf8 encoding

See the full changelog: https://nodejs.org/en/blog/release/v19.2.0/

npm workspaces: npm run and exec

Ruy Adorno — Wed, 24 Mar 2021 12:43:15 +0000

I bring good news!

Workspaces support for both npm run and npm exec landed today in npm@7.7.0, it adds the new -w and -ws config options that allows for running scripts in workspaces from the top-level folder, e.g:

assuming a file structure:

.
├── package.json ->  { "workspaces": ["packages/*"] }
└── packages
    ├── a
    │   ├── index.js
    │   └── package.json
    ├── b
    │   ├── index.js
    │   └── package.json
    └── c
        ├── index.js
        └── package.json

It's now possible to run a script in a given workspace. In order to run one of the scripts available in the workspace named a, at location: ./packages/a/ you may run from the root of your project, either of the following:

npm run <script-name> -w a
npm run <script-name> -w ./packages/a

It also supports the test|start|stop|restart top level comands, so if you're using any of these you can just add -w <workspaces-name> and it should work as expected, e.g:

npm test -w a (will run the tests of workspace a)

In case you want to run a script against all the configured workspaces, there's a workspaces configuration option that enables just that:

npm test -ws

Lastly it's also possible to run scripts in a group of workspaces by using the path to their parent folder as the workspace config value. That means running npm test -w ./packages will run tests in all workspaces nested at the ./packages location.

Want to learn more about it?

We updated the docs, see:

npm run docs: https://docs.npmjs.com/cli/v7/commands/npm-run-script#workspaces-support
npm exec docs: https://docs.npmjs.com/cli/v7/commands/npm-exec#workspaces-support
workspaces docs: https://docs.npmjs.com/cli/v7/using-npm/workspaces

You may also want to check out the changelog:

https://github.com/npm/cli/releases/tag/v7.7.0

npm diff

Ruy Adorno — Mon, 01 Feb 2021 14:16:00 +0000

The npm cli just added a new npm diff command that show changes between registry-published tarballs, similar to git diff but tracking versions of packages in the registry instead of commits.

Introducing npm diff

The idea for a npm diff command has been around since last year when I first wrote a npm diff RFC that got rather positive feedback from the community.

Providing more transparency to changes to packages installed in a given project was the main motivation but being a package author myself, I quickly saw a chance to improve package maintainers' lives by also having workflows to compare the contents of the package you're currently working on.

Following up are some examples of how to use npm diff in both the package consumer and package author scenarios.

Diffing packages from the registry

You can point to any two different published package versions and get git-like patch output that shows the difference between file contents in them.

Example:

$ npm diff --diff=ntl@5.0.0 --diff=ntl@5.1.0
diff --git a/README.md b/README.md
index v5.0.0..v5.1.0 100644
--  a/README.md
+++ b/README.md
@@ -36,6 +36,7 @@
     + [UI Size](#ui-size)
   * [Repeat the last ran task](#arrows_counterclockwise-repeat-the-last-ran-task)
   * [Run multiple tasks](#m-run-multiple-tasks)
+    + [Preserve selection order](#run-multiple-tasks-in-order-of-selection)
   * [Run in autocomplete or fuzzy search mode](#fast_forward-run-in-autocomplete-or-fuzzy-search-mode)
   * [Tips](#white_check_mark-tips)
     + [ntl as default task](#ntl-as-default-task)
@@ -85,7 +86,9 @@
 - Multiple interactive interfaces (menu list, autocomplete fuzzy search)
 - Many options to customize the UI (exclude scripts, amount of items, etc)
 - Easy to repeat last ran script (`nt` and `rerun` options)
-- Run multiple tasks (can also easily repeat multiple ran tasks)
+- Run multiple tasks
+  - Repeat previously set of ran tasks
+  - Preserve order of selection
 - Customize rerun cache options

Keep in mind the --diff arguments accepts any valid npm install arguments meaning that you can also target local folders or git repositories on top of using semver ranges and registry tags.

Diffing packages you're updating

Using a single argument is a handy shortcut to diff the contents of a local installed package to the contents you'd get with the version specified by the --diff option.

It also provides a shortcut that replicates the logic of the wanted version returned by npm outdated when using only the package name and omitting any version/tags. Example:

$ npm diff --diff=abbrev
diff --git a/package.json b/package.json
index v1.1.0..v1.1.1 100644
--  a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "abbrev",
-  "version": "1.1.0",
+  "version": "1.1.1",
   "description": "Like ruby's abbrev module, but in js",
   "author": "Isaac Z. Schlueter <i@izs.me>",
   "main": "abbrev.js",

Diffing local changes to a package

This is the workflow package authors will find the most helpful. When working on a package that is published to the registry, you can get a diff output between the contents from you local file system comparing it to the latest published version by just running npm diff (no arguments).

$ npm diff
diff --git a/package.json b/package.json
index v3.1.1..v3.2.0-beta.1 100644
--  a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "ipt",
-  "version": "3.1.1",
+  "version": "3.2.0-beta.1",
   "description": "iPipeTo - The Node.js cli interactive workflow",
   "repository": "ruyadorno/ipt",
   "author": {

Filter by file names

In some cases the full diff patch output might be too verbose and you're only interested in a single file or folder, in that case you can provide these path names as positional arguments and they will be treated as filters limiting the output to only contents of the files defined in these patterns (similar to how git diff works).

e.g: use npm diff package.json to only print diffs in the package.json file, npm diff lib/ to limit diff output to files inside a lib folder.

More options

A few more options from git diff are implemented, such as a --diff-name-only flag to only print the file names of changed files, or --diff-ignore-all-space very useful to ignore padding spaces/tabs and print shorter diff outputs.

If you want to learn more about the different options, make sure to read the npm diff docs. 😊

⬇️ Get it now

npm diff was introduced in npm@7.5.0, to make sure you have the latest v7 version install it now with:

$ npm install -g npm@7

- Happy diffing everyone!

npm7 Highlights in 1min

Ruy Adorno — Wed, 28 Oct 2020 15:42:20 +0000

Hey folks!

I presented at a GitHub virtual meetup a quick demonstration of the highlights in npm7 and thought it would be nice to add bullet points and make it a quick visual reference for folks who want a 1min tour of how the new (and tweaked) features look like.

Click here (or at the image below) in order to see the slides over at SpeakerDeck 😊

Also dropped the link on Twitter:

Ruy Adorno

@ruyadorno

Took some time to add notes to the npm7 Highlights slide deck presented yesterday in the GitHub Presente! Online Meetup 😄

Make sure to check it out: speakerdeck.com/ruyadorno/npm-…

12:00 PM - 28 Oct 2020

Hope you find it useful 😃

Announcing npm7

Ruy Adorno — Tue, 13 Oct 2020 18:14:00 +0000

It's been a very long and crazy ride but I'm happy to share that the project I've been working so hard since I joined the npm team more than an year ago is finally out! npm7 is the new major version of the npm cli 😍

TLDR; npm install -g npm@7

What's new?

First let's highlight the major additions:

workspaces! finally the top-requested feature from our userbase makes its way into a stable release line 🎉
auto-installing peer-dependencies again 📦

Improving DX

There are some smaller changes/additions/tweaks that will hopefully continue to help improving the user experience, such as:

new npm exec command - same as npx that now lives in the cli 😁
a new package-lock format and support to install from yarn.lock files 🚀
improved npm audit output! 😎
new update notification system for the npm cli
ability to install a git/GH pkg from a PR: npm i user/project#pull/123
less verbose install output
skip pre/post scripts when using --ignore-scripts
new system to cache node_modules data that makes npm ls much faster
npm ls now defaults to top-level deps only, to see the entire tree you can now run npm ls --all
slightly improved npm fund output, highlighting funding urls and properly nesting deps
And much, much more!

Clean up work

In reality npm7 is the long due refactor/clean up of the npm cli and it spawns a couple of very important internal packages to our ecosystem which are now the standard Programmatic APIs for npm:

@npmcli/arborist the new npm install system
@npmcli/config the new npm config
@npmcli/run-script the new npm run
@npmcli/map-workspaces read workspaces configs
libnpmfund npm fund Programmatic API

I'm really excited to see what this will enable in the community, for the first time it's going to be a trivial thing to require('@npmcli/arborist') and have the same npm install experience from within userland scripts without the need of spawning any subprocesses 🤩

It's also worth mentioning that a lot of the work that went into this version is making sure every line of code and functionality is well-tested and stable so that we can better iterate on new features and bug fixes moving forward 😊

More?

There are also new options/flags that goes along with some of the new features such as --legacy-peer-deps and --strict-peer-deps that help tweak the behavior of installing peer deps, npm ls --all to see all installed deps since the default is now show top-level only, etc

The team will be working hard on adding more tests and fixing any bugs that managed to slip through our beta test period 😄 Feel free to reach out to us in our GitHub issue tracker that now have the best up-to-date links on how to report bugs, propose new features or get help.

You can also read more about the release in the official channels:

⬇️ Get it now

The npm7 is going to be a part of the upcoming node15 release but if you want to get it first, you can install it now with:

npm install -g npm@7

Happy dependency-installing everyone!

npm@6.14.8

Ruy Adorno — Mon, 17 Aug 2020 21:52:19 +0000

We just shipped a new version of the npm cli!

⬇️ Get it now:

npm i -g npm@latest

To check the full changelog, check out the blog post in the official blog.

And that's it! 😎 Have an awesome week everyone!

Photo by Kelly Sikkema on Unsplash

Announcing the npm@7 beta!

Ruy Adorno — Tue, 11 Aug 2020 17:19:44 +0000

We have just released the beta version of npm v7 🎉

It has workspaces support along with many refactors that aim to make npm better and better in the future 😎

Are you feeling adventurous? Want to check out all the improvements?

⬇️ Get it now:

npm i -g npm@next-7

Make sure to also read the official announcement and check the full list of breaking changes in the npm blog ❤️

🐛 Found any nasty bug?

This is the first release of a beta version and as such it's expected that there will still be problems to be found and things to be polished.

Found any issues? Let us know!

Have fun! 🚀

Cover image photo by James Pond on Unsplash

npm@6.13.6

Ruy Adorno — Thu, 09 Jan 2020 23:35:41 +0000

We just shipped a new npm version 🚀

Go ahead and get it in the usual ways:

npm install -g npm@latest

This release contain some bug fixes, including an important one that fixes issues using npm within docker containers to install new packages.

You can see the full changelog in the npm blog: https://blog.npmjs.org/post/190165702645/release-6136

Node+JS Interactive 2019 talks

Ruy Adorno — Wed, 08 Jan 2020 21:56:11 +0000

All talks from last Node+JS Interactive 2019 conference in Montreal are now available on Youtube! You can check the full playlist here:

https://www.youtube.com/playlist?list=PLfMzBWSH11xZPfWcC0DqFqKo_reMP58mw

$ cli --tools --for all-the-things

Ruy Adorno — Tue, 07 Jan 2020 13:05:37 +0000

Turns out my talk at Node JS Interactive 2019 was not a completely failure! 🎉 yay! 🎉

So as a reward I get to have a decent Youtube video of me presenting at a major conference that I can actually share with the world! ❤️ Are you interested in the intersection of cli + JavaScript + Node.js? Or just a friend that wants to see me nervously trying to live code stuff in front of a big crowd? In any case here is the video, enjoy it 😄

PS: Slides are available on SpeakerDeck, you can browse them here:

Node+JS Interactive

Ruy Adorno — Wed, 11 Dec 2019 15:33:11 +0000

Hi y'all, this week my home city is hosting the largest OpenJS foundation event Node+JS Interactive ❤️ if you're around make sure to stop by and say hi! I might have some npm swag too 😁

Feel free to poke me on Twitter. Have a great conference week for those of you who are around!

Sneak peek of the new npm docs website

Ruy Adorno — Wed, 04 Dec 2019 16:44:37 +0000

Hi y’all, you probably don’t know yet but there’s a refresh of the npm docs website coming to you 😊

A preview is available here: https://preview-docs.npmjs.com/cli-commands/npm

Feel free to provide feedback in the comments and I’ll do my best to forward it to the rest of the team 😄

DEV Community: Ruy Adorno

Node.js v19.2.0 Release

Notable changes:

buffer:

deps:

doc:

util:

npm workspaces: npm run and exec

I bring good news!

Want to learn more about it?

npm diff

Introducing npm diff

Diffing packages from the registry

Diffing packages you're updating

Diffing local changes to a package

Filter by file names

More options

⬇️ Get it now

- Happy diffing everyone!

npm7 Highlights in 1min

Announcing npm7

What's new?

Improving DX

Clean up work

More?

⬇️ Get it now

Happy dependency-installing everyone!

npm@6.14.8

Announcing the npm@7 beta!

⬇️ Get it now:

🐛 Found any nasty bug?

Have fun! 🚀

Cover image photo by James Pond on Unsplash

npm@6.13.6

Node+JS Interactive 2019 talks

$ cli --tools --for all-the-things

Links

Node+JS Interactive

Sneak peek of the new npm docs website