storybookjs/storybook

[Bug]: NextJS automigration misses static paths

Open

#21,492 建立於 2023年3月9日

在 GitHub 查看
 (0 留言) (1 反應) (0 負責人)TypeScript (89,909 star) (10,058 fork)batch import
automigrationsbughas workaroundhelp wantedsev:S3

描述

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

貢獻者指南

技術棧
nextjstypescriptreact
領域
frontend
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Storybook basicsNextJS static files
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
40
研究方向
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.
[Bug]: NextJS automigration misses static paths · storybookjs/storybook#21492 | Good First Issue