-
-
Notifications
You must be signed in to change notification settings - Fork 36
fix: dynamically suggest package manager installation command in migrate
scripts
#495
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
Conversation
🦋 Changeset detectedLatest commit: 8717b7f The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
commit: |
migrate
script
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your pr!
detect
is determining the package manager based on existing or non existing lockfiles like pnpm-lock.yml
etc. getUserAgent
determines with which package manager the current command is being executed.
Since svelte-migrate
is expected to be run on an existing project, it's totally valid to use detect
here in my opinion.
migrate
scriptmigrate
scripts
Relates #187
Had to add package-manager-detector to the migrate package as a dependency.
I was a little confused on using
detect
vs.getUserAgent
--maybe you have a better understanding of when and where to use each? For this I used the barebonesdetect
and it worked on my machine.