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

How to solve the console preload crossorigin warning problem #536

Open
5 of 7 tasks
nekorrrr opened this issue May 21, 2024 · 1 comment
Open
5 of 7 tasks

How to solve the console preload crossorigin warning problem #536

nekorrrr opened this issue May 21, 2024 · 1 comment

Comments

@nekorrrr
Copy link

Describe the bug

image

vitesse Demo: https://vitesse.netlify.app/

Reproduction

this project

System Info

vitesse.netlify.app/:1  A preload for 'https://vitesse.netlify.app/assets/app-Ccandkqr.css' is found, but is not used because the request credentials mode does not match. Consider taking a look at crossorigin attribute.
vitesse.netlify.app/:1  The resource https://vitesse.netlify.app/assets/app-Ccandkqr.css was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.
vitesse.netlify.app/:1  A preload for 'https://vitesse.netlify.app/assets/app-Ccandkqr.css' is found, but is not used because the request credentials mode does not match. Consider taking a look at crossorigin attribute.
vitesse.netlify.app/:1  The resource https://vitesse.netlify.app/assets/app-Ccandkqr.css was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.

Used Package Manager

pnpm

Validations

  • Follow our Code of Conduct
  • Read the Contributing Guide.
  • Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
  • Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
  • The provided reproduction is a minimal reproducible of the bug.

Contributions

  • I am willing to submit a PR to fix this issue
  • I am willing to submit a PR with failing tests (actually just go ahead and do it, thanks!)
@nekorrrr
Copy link
Author

@antfu @YunYouJun @hannoeru

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

No branches or pull requests

1 participant