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.