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 (89,909 stars) (10,058 forks)batch import
automigrationsbughas workaroundhelp wantedsev:S3

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

Tech stack
nextjstypescriptreact
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.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Storybook basicsNextJS static files
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate how Storybook's NextJS automigration handles static directories. Look at the migration logic in `code/frameworks/nextjs` and compare with the webpack5 configuration. The user reports that importing assets into stories failed after switching to NextJS framework but using a string path to the static directory worked. The automigration likely misses the `staticDirs` configuration. Check if there's a missing transformation or if the static directory path is not being passed correctly. Refer to the issue for the user's feedback and examine the relevant code files.