Skip to content
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

Assets referencing libraries with bare specifiers in HTML do not work in dev #12260

Open
7 tasks done
lovetingyuan opened this issue Mar 2, 2023 · 1 comment · May be fixed by #12334
Open
7 tasks done

Assets referencing libraries with bare specifiers in HTML do not work in dev #12260

lovetingyuan opened this issue Mar 2, 2023 · 1 comment · May be fixed by #12334
Labels
feat: html inconsistency Inconsistency between dev & build

Comments

@lovetingyuan
Copy link

Describe the bug

I use <link rel="stylesheet" href="normalize.css"> in index.html,
but this css is 404 in development but got processed in production build.
I think it is inconsistent behavior.

Reproduction

https://stackblitz.com/edit/vitejs-vite-yegqau

Steps to reproduce

  1. npm run dev, the css is lost
  2. npm run build && npm run preview, the css works well.

It is inconsistent behavior.

System Info

-

Used Package Manager

npm

Logs

No response

Validations

@stackblitz
Copy link

stackblitz bot commented Mar 2, 2023

Fix this issue in StackBlitz Codeflow Start a new pull request in StackBlitz Codeflow.

@bluwy bluwy added feat: css inconsistency Inconsistency between dev & build and removed pending triage labels Mar 2, 2023
@sun0day sun0day linked a pull request Mar 8, 2023 that will close this issue
9 tasks
@bluwy bluwy changed the title link css in index.html is inconsistent between development and production build Assets referencing libraries with bare specifiers in HTML do not work in dev Oct 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat: html inconsistency Inconsistency between dev & build
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants