-
Notifications
You must be signed in to change notification settings - Fork 708
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
Even though Yarn is detected, it creates a npm lockfile #747
Comments
This can be solved with a simple child process check. But I would maybe give the user an option to choose. At one point Yarn made a lot of sense but the tables have turned and NPM has caught up to Yarn. It provides some additional functionality like For this reason I would let users choose between
If you are OK with this I can get right on it @silvenon. |
@ilicmarko thanks a lot for your support :-) Maybe it is better to handle first this bug and in a separate issue/PR we can discuss about let the user choose the CLI ;-) What do you think @silvenon ? |
@ilicmarko I like the idea, are you still up for doing this? |
@silvenon I will sit down on the weekend and put in some work. |
Sorry for a delay, had some construction work in the house so no JS for me :( Anyways, got something done after work. It was really strange to debug as the Lines 23 to 31 in c62391b
It's interesting that even if you send the Looking at line 86. Anyways what do you suggest as the fix? |
Sorry for my late response 😅 Thank you for figuring out where the error is coming from! 🏆 We definitely need to add Yarn support to those generators, feel free to send PRs there if you're up for it. As for the |
No description provided.
The text was updated successfully, but these errors were encountered: