Skip to content

Unknown package manager #73

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

Open
Akimotorakiyu opened this issue Feb 15, 2025 · 3 comments · May be fixed by #74 or #75
Open

Unknown package manager #73

Akimotorakiyu opened this issue Feb 15, 2025 · 3 comments · May be fixed by #74 or #75

Comments

@Akimotorakiyu
Copy link

Describe the bug
A clear and concise description of what the bug is.

Image

To Reproduce
Steps to reproduce the behavior:

pnpm create pylon@latest

or

npm create pylon@latest

Screenshots
Image

Desktop (please complete the following information):

  • OS: [e.g. iOS] mac os 14
@Akimotorakiyu
Copy link
Author

It is recommended to allow users to choose their own package manager.

@schettn
Copy link
Contributor

schettn commented Feb 17, 2025

Hi @Akimotorakiyu, yes a unknown PM should not throw an error, I have opened a PR to fix that. But I am curious why it cannot detect the PM. You have pnpm and npm installed right?

@Akimotorakiyu
Copy link
Author

Akimotorakiyu commented Feb 17, 2025

@schettn yes, i'm coding at a pnpm mono repo, pnpm is works well.

@schettn schettn linked a pull request Feb 19, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants