storybookjs/storybook

[Bug]: NextJS automigration misses static paths

Open

#21,492 opened on Mar 9, 2023

View on GitHub
 (0 comments) (1 reaction) (0 assignees)TypeScript (10,058 forks)batch import
automigrationsbughas workaroundhelp wantedsev:S3

Repository metrics

Stars
 (89,909 stars)
PR merge metrics
 (Avg merge 9d 3h) (173 merged PRs in 30d)

Description

Describe the bug

Feedback from @thafryer on upgrading Chromatic's storybook:

When I switched to the NextJS framework, importing assets into stories  stopped working. This was working when I was using react-webpack5 as the framework. i switched to pointing a string path to the static directory, which worked.

To Reproduce

No response

System

No response

Additional context

No response

Contributor guide

Research direction
Compare the static asset handling between the NextJS framework and the react webpack5 framework in Storybook. Check how the NextJS plugin resolves static directories and asset imports.
Tech stack
typescriptreactnextjs
Domain
frontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
StorybookNextJS
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40