Skip to content

Fixed an issue with projects using npm workspaces being recognized as yarn projects #250

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

Merged
merged 3 commits into from
Apr 29, 2025

Conversation

Andarist
Copy link
Collaborator

@Andarist Andarist commented Apr 27, 2025

see #245 (comment)
fixes #97

@Andarist Andarist requested a review from emmatown April 27, 2025 08:30
Copy link

changeset-bot bot commented Apr 27, 2025

🦋 Changeset detected

Latest commit: cff6c02

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 4 packages
Name Type
@manypkg/get-packages Major
@manypkg/find-root Major
@manypkg/tools Major
@manypkg/cli Patch

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

@Andarist Andarist mentioned this pull request Apr 27, 2025
Copy link

socket-security bot commented Apr 27, 2025

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addednpm-workspace-base-pkg-b@​1.0.0100100100100100

View full report

@bluwy
Copy link
Contributor

bluwy commented Apr 27, 2025

I think this should also address #97

@Andarist
Copy link
Collaborator Author

I pushed an extra fix to make this happen. It still won't work for non-monorepos that are detected as "root" and mapped to yarn there. There is no point in using manypkg itself with a single-package repository though but this is certainly weird and wrong in the general sense.

Copy link
Member

@emmatown emmatown left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

besides the comment, looks good

@@ -18,6 +18,7 @@ export async function install(toolType: string, cwd: string) {
const cliRunners: Record<string, string> = {
bolt: "bolt",
lerna: "lerna",
npm: "npm",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think the condition below for pnpm needs to apply for npm as well

@Andarist Andarist merged commit 3cf8c4e into main Apr 29, 2025
6 checks passed
@Andarist Andarist deleted the npm-tool branch April 29, 2025 16:37
@github-actions github-actions bot mentioned this pull request Apr 29, 2025
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

Successfully merging this pull request may close these issues.

Does this work with npm?
3 participants