-
Notifications
You must be signed in to change notification settings - Fork 53
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
Conversation
🦋 Changeset detectedLatest commit: cff6c02 The changes in this PR will be included in the next version bump. This PR includes changesets to release 4 packages
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 |
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
I think this should also address #97 |
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 |
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.
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", |
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.
i think the condition below for pnpm needs to apply for npm as well
see #245 (comment)
fixes #97