Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add info to readme about NPM@7 symlink changes #15

Open
Venryx opened this issue Feb 22, 2021 · 3 comments
Open

Add info to readme about NPM@7 symlink changes #15

Venryx opened this issue Feb 22, 2021 · 3 comments

Comments

@Venryx
Copy link
Contributor

Venryx commented Feb 22, 2021

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)

@UD-UD
Copy link
Owner

UD-UD commented Feb 22, 2021

@Venryx Thanks for the update. Let me know the changes relevant to this utility. I will take proper steps and update the ReadMe accordingly.

@Venryx
Copy link
Contributor Author

Venryx commented Mar 29, 2021

Recent issue I just found for it: npm/cli#2372

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.)

@Venryx
Copy link
Contributor Author

Venryx commented May 18, 2021

Looks like the bug is still not fixed. 😔

See recent posts in this thread for details: npm/cli#2372

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants