"d3@5" would not resolve to "d3@6.1.1"

Fixed, thanks.

Now I kind of want to publish a npm module named "not-a-real-npm-module". 😁

Added a scope to prevent this. 😛

Looks like this no longer works?

Yes, fixed. Also added a note that this is an antipattern since new versions can introduce breaking changes exactly like this.

looks to be an error here as well