Note, this is a rarely used feature that should be aggressively avoided, but it‘s important to minimize gaps between node and this package.
Fixes #163.
I'm uncertain if I'll backport this to the 1.x branch, primarily because of the risk of unintentional breakage. However, since virtually nobody is going to be using these directories, and since it's only going to potentially start resolving bare specifiers where previously there was an error, this does seem safe.
Note, this is a rarely used feature that should be aggressively avoided, but it‘s important to minimize gaps between node and this package.
Fixes #163.
I'm uncertain if I'll backport this to the 1.x branch, primarily because of the risk of unintentional breakage. However, since virtually nobody is going to be using these directories, and since it's only going to potentially start resolving bare specifiers where previously there was an error, this does seem safe.