storybookjs/storybook

[Bug]: NextJS automigration misses static paths

Open

Aperta il 9 mar 2023

Vedi su GitHub
 (0 commenti) (1 reazione) (0 assegnatari)TypeScript (89.909 star) (10.058 fork)batch import
automigrationsbughas workaroundhelp wantedsev:S3

Descrizione

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

Guida contributor

Tech stack
nextjstypescriptreact
Dominio
frontend
Tipo issue
bug
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
3
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
half day
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
stale
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
mostly clear
Prerequisiti
Storybook basicsNextJS static files
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
40
Direzione di ricerca
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.