Skip to content

[v4.0.8] Storybook + Vite crashes if filename contains # #16877

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
deebov opened this issue Feb 28, 2025 · 3 comments · Fixed by #16957
Closed

[v4.0.8] Storybook + Vite crashes if filename contains # #16877

deebov opened this issue Feb 28, 2025 · 3 comments · Fixed by #16957

Comments

@deebov
Copy link
Contributor

deebov commented Feb 28, 2025

What version of Tailwind CSS are you using?

4.0.9

What build tool (or framework if it abstracts the build tool) are you using?

bun, vite, storybook

What version of Node.js are you using?

bun 1.2.4

What operating system are you using?

macOS

Reproduction URL

Instructions are included in the repo README:

https://github.com/deebov/storybook-vite-issue-reproduction

Issue description

Starting the version 4.0.8 storybook crashes if a filename contains # in public folder. You can clearly reproduce this in the repo provided above.

@philipp-spiess
Copy link
Member

Hey! I am able to reproduce this with pure Vite APIs so this seems to be an upstream issue. I tried a few workarounds but nothing seemed to make the file properly watched. Filed an upstream issue: vitejs/vite#19563

@deebov
Copy link
Contributor Author

deebov commented Mar 5, 2025

Interesting, because this started happening only after 4.0.8 which also introduced other Vite related bugs.

@philipp-spiess
Copy link
Member

@deebov Yeah it's because we didn't use that API before. BTW This only is an issue for .svg files it seems. We can probably work around it by not watching .svg files containing a # for changes in class names which might be reasonable for the time being.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants