You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NPM v7 has apparently made significant changes to the npm link command. These can be seen be opening the changelog file, and searching the page for "link". (some matches are related [like the switch from Symbolic Links to Junctions], others are unrelated)
There are a half dozen or so changes, some of which are potentially relevant to this utility's functionality. (Perhaps even removing the need for it! Though let's not get ahead of ourselves, since I haven't tested it yet -- do to having quite a few globally-installed packages that I don't want to copy to the new version right now.)
Anyway, it would be nice if someone could do an evaluation of the npm-link-related changes in version 7, to see how it impacts the functionality and/or need for the npm-safe-install utility.
(I say "someone", but most likely this will be me -- when I finally have the time/motivation to do that testing. :P)
The text was updated successfully, but these errors were encountered:
It looks like the bug may have finally been fixed between [email protected] and [email protected]. (it wasn't confirmed fixed by the issue creator, but the npm dev's saying a set of changes might have fixed it, combined with a lack of follow up by the issue creator, suggests it may have been)
(At some point it will be good to confirm, but I've linked the above in the meantime; haven't tested myself yet because I need to set aside time to re-install my global dependencies when I do.)
NPM v7 has apparently made significant changes to the
npm link
command. These can be seen be opening the changelog file, and searching the page for "link". (some matches are related [like the switch from Symbolic Links to Junctions], others are unrelated)There are a half dozen or so changes, some of which are potentially relevant to this utility's functionality. (Perhaps even removing the need for it! Though let's not get ahead of ourselves, since I haven't tested it yet -- do to having quite a few globally-installed packages that I don't want to copy to the new version right now.)
Anyway, it would be nice if someone could do an evaluation of the npm-link-related changes in version 7, to see how it impacts the functionality and/or need for the
npm-safe-install
utility.(I say "someone", but most likely this will be me -- when I finally have the time/motivation to do that testing. :P)
The text was updated successfully, but these errors were encountered: