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.

Sign up for GitHub

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

Jump to bottom

adds support for legacy-peer-deps flag on npm install #4

Merged
merged 1 commit into from
Jan 2, 2023
Merged

adds support for legacy-peer-deps flag on npm install #4

merged 1 commit into from
Jan 2, 2023

Conversation

MiniDigger
Copy link
Owner

@MiniDigger MiniDigger merged commit 4dce0e8 into master Jan 2, 2023
@MiniDigger MiniDigger deleted the legacy-peer-deps-support branch January 2, 2023 14:22
@Nefcanto
Copy link

How does it work?

@MiniDigger
Copy link
Owner Author

npx npm-check-updated -u --legacy-peer-deps

@Nefcanto
Copy link

@MiniDigger so that the command is changed from npm-check to npm-check-updated. Is that a good decision? Why not having the original command?

@Nefcanto
Copy link

@MiniDigger I got this error:

Need to install the following packages:
[email protected]
Ok to proceed? (y) y
⠦ Checking npm registries for updated packages.Invalid Version: 2021.08.30
For more detail, add `--debug` to the command

@MiniDigger
Copy link
Owner Author

For more detail, add --debug to the command

@MiniDigger
Copy link
Owner Author

MiniDigger commented Oct 28, 2023 •
edited
Loading

@MiniDigger so that the command is changed from npm-check to npm-check-updated. Is that a good decision? Why not having the original command?

I dont control the original repo, I just forked it for my own usage

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@MiniDigger @Nefcanto