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

Misleading package, consider deprecate #4

Open
M-jerez opened this issue Apr 11, 2020 · 1 comment
Open

Misleading package, consider deprecate #4

M-jerez opened this issue Apr 11, 2020 · 1 comment

Comments

@M-jerez
Copy link

M-jerez commented Apr 11, 2020

Apologies if I'm wrong.

But how is the functionality of this package different than running:

npm link . & npm link <my_own_packagename>

if is the same functionality please consider deprecating the package and update the readme to reflect this.
This package was the first result after search 'npm self link' and might be misleading other devs, as it is not required at all.

@Andarist
Copy link
Owner

From what I recall running npm link in a package with the already existing link was causing problems for me - build scripts running unnecessarily and similar.

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