Skip to content

Conversation

yatishgoel
Copy link
Contributor

@yatishgoel yatishgoel commented Apr 26, 2025

Closes #30390

What I did

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 PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the @storybookjs/core team here.

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

Greptile Summary

Added mock implementation and webpack alias mappings for Next.js Link component to fix navigation issues in Next.js 15 with appDirectory configuration.

  • Added code/frameworks/nextjs/src/export-mocks/link/index.tsx with mock Link component implementation
  • Added Link component mappings in code/frameworks/nextjs/src/export-mocks/webpack.ts for proper aliasing
  • Updated code/frameworks/nextjs/package.json exports to include new Link mock component
  • Added support for Next.js 15.0.0 as peer dependency

The changes ensure proper Link component behavior in stories by preventing navigation to non-existent pages when using Next.js 15 in appDirectory mode.

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.

LGTM

3 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile

Copy link

nx-cloud bot commented Apr 26, 2025

View your CI Pipeline Execution ↗ for commit f9534d8.

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

☁️ Nx Cloud last updated this comment at 2025-07-02 08:26:31 UTC

@valentinpalkovic valentinpalkovic added the patch:yes Bugfix & documentation PR that need to be picked to main branch label Jun 23, 2025
@valentinpalkovic
Copy link
Contributor

Hi @yatishgoel,

Thank you for opening the PR!

Could you take a look at the build pipeline? Unfortunately, it is failing.

@github-actions github-actions bot added the Stale label Jul 18, 2025
@valentinpalkovic
Copy link
Contributor

Superseded by #32131

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug ci:normal nextjs patch:yes Bugfix & documentation PR that need to be picked to main branch Stale
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: Next.js Link component causes navigation to a non-existent page in stories
2 participants