Skip to content

Core: Enhance package manager install methods to support optional force flag #31796

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

Conversation

valentinpalkovic
Copy link
Contributor

@valentinpalkovic valentinpalkovic commented Jun 17, 2025

Closes #

What I did

When upgrading dependencies, for npm users we always install dependencies with the --force flag set to circumvent the issue described here npm/cli#8059

Checklist for Contributors

Testing

The changes in this PR are covered in the following automated tests:

  • stories
  • unit tests
  • integration tests
  • end-to-end tests

Manual testing

This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!

Documentation

  • Add or update documentation reflecting your changes
  • If you are deprecating/removing a feature, make sure to update
    MIGRATION.MD

Checklist for Maintainers

  • When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli-storybook/src/sandbox-templates.ts

  • Make sure this PR contains one of the labels below:

    Available labels
    • bug: Internal changes that fixes incorrect behavior.
    • maintenance: User-facing maintenance tasks.
    • dependencies: Upgrading (sometimes downgrading) dependencies.
    • build: Internal-facing build tooling & test updates. Will not show up in release changelog.
    • cleanup: Minor cleanup style change. Will not show up in release changelog.
    • documentation: Documentation only changes. Will not show up in release changelog.
    • feature request: Introducing a new feature.
    • BREAKING CHANGE: Changes that break compatibility in some way with current major version.
    • other: Changes that don't fit in the above categories.

🦋 Canary release

This pull request has been released as version 0.0.0-pr-31796-sha-819607ae. Try it out in a new sandbox by running npx [email protected] sandbox or in an existing project with npx [email protected] upgrade.

More information
Published version 0.0.0-pr-31796-sha-819607ae
Triggered by @valentinpalkovic
Repository storybookjs/storybook
Branch valentin/circumvent-npm-peer-dep-error-during-upgrade
Commit 819607ae
Datetime Tue Jun 17 10:02:35 UTC 2025 (1750154555)
Workflow run 15704238128

To request a new release of this pull request, mention the @storybookjs/core team.

core team members can create a new canary release here or locally with gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=31796

Greptile Summary

Enhances package manager install methods with a force flag option to address npm peer dependency issues during upgrades, particularly npm/cli#8059.

  • Modified JsPackageManager base class to support optional force flag in installDependencies and runInstall methods
  • Implemented force flag support across package manager proxies (NPM, PNPM, Yarn1, BUN)
  • Updated upgrade.ts to automatically use --force flag for npm installations
  • Changes affect installation behavior only for npm users while maintaining existing behavior for other package managers

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

6 files reviewed, 1 comment
Edit PR Review Bot Settings | Greptile

Copy link

nx-cloud bot commented Jun 17, 2025

View your CI Pipeline Execution ↗ for commit 819607a.

Command Status Duration Result
nx run-many -t build --parallel=3 ✅ Succeeded 1m 17s View ↗

☁️ Nx Cloud last updated this comment at 2025-06-17 10:09:34 UTC

valentinpalkovic and others added 3 commits June 17, 2025 09:31
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
@valentinpalkovic valentinpalkovic merged commit c8f2db1 into next Jun 17, 2025
55 of 58 checks passed
@valentinpalkovic valentinpalkovic deleted the valentin/circumvent-npm-peer-dep-error-during-upgrade branch June 17, 2025 12:44
@valentinpalkovic valentinpalkovic added the patch:yes Bugfix & documentation PR that need to be picked to main branch label Jun 17, 2025
@github-actions github-actions bot mentioned this pull request Jun 17, 2025
15 tasks
valentinpalkovic added a commit that referenced this pull request Jun 17, 2025
…er-dep-error-during-upgrade

Core: Enhance package manager install methods to support optional force flag
(cherry picked from commit c8f2db1)
@github-actions github-actions bot mentioned this pull request Jun 18, 2025
15 tasks
@github-actions github-actions bot added the patch:done Patch/release PRs already cherry-picked to main/release branch label Jun 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug ci:normal patch:done Patch/release PRs already cherry-picked to main/release branch patch:yes Bugfix & documentation PR that need to be picked to main branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants