codesandbox / codesandbox/codesandbox-client
service-worker.js not found
Open
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
I tried to run codesandbox-client lollcaly, and I found several problems:
- I use nodejs 16.13.1, but the lru-cache 10.0.1 need. node version >= 16.14, so I reinstall nodejs 16.14.2 .
- after yarn install; yarn start, I open http://localhost:3000 with browser, but I found 404 error for. service-worker.js. and manifest.json . these files are under 'www' folder, I'm not sure why these files can't be find
- I create a. sandbox of. 'HTML&CSS', after redirect to this sandbox, the content is 'Whoops, page not found We can’t seem to find the page you’re looking for'.
How has this issue affected you? What are you trying to accomplish?
To Reproduce
Link to sandbox: link (optional)
Your Environment
| Software | Name/Version |
|---|---|
| Сodesandbox | main/latest |
| Browser | chrome |
| Operating System | macos |
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
Reproduce the reported setup with yarn install, yarn start, and http://localhost:3000. Inspect how the named service-worker.js and manifest.json files under www are served, then check the HTML&CSS sandbox redirect; done means the assets load without 404s and the sandbox no longer shows the page-not-found response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100