codesandbox / codesandbox/codesandbox-client
<link rel="preload" with "as" doesn't work printing The resource https://qm3w7j.csb.app/styles.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.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13.6k
- Forks
- 2.4k
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 2
Description
🐛 bug report
Preflight Checklist
- I have read the Contributing Guidelines for this project.
- I agree to follow the Code of Conduct that this project
adheres to. - I have searched the issue tracker for an issue that matches the one I want
to file, without success.
Description of the problem
It looks like <link rel="preload" with as="style" and as="script" doesn't work.
How has this issue affected you? What are you trying to accomplish?
Having a minimal code example with <link rel="preload" href="styles.css" as="style" /> & <link rel="preload" href="script.js" as="script" />.
To Reproduce
https://codesandbox.io/p/sandbox/104-html-performance-optimization-techniques-qm3w7j / https://qm3w7j.csb.app and check the console, which will print The resource https://qm3w7j.csb.app/styles.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.
Link to sandbox: link (optional)
Your Environment
| Software | Name/Version |
|---|---|
| Сodesandbox | latest |
| Browser | any |
| Operating System | most likely any |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report names only the CodeSandbox reproduction at https://qm3w7j.csb.app and the preload tags for styles.css and script.js; no repository files or tests are identified. Start by opening the sandbox, checking the console and network activity, and comparing the preload declarations with when those resources are used. Done would require determining the cause of the warning and defining a verified correction, but the issue does not specify the intended code change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, html, javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100