codesandbox / codesandbox/codesandbox-client
Caching for files too aggressive
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13.6k
- Forks
- 2.4k
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 2
Description
I have a small sandbox where I deleted some html file which is used by my framework (node based compiler for HTML), It basically goes trough the file-system and builds an ui from the templates it finds, I moved some files around changed them deleted them and then added the same file back with the same name now the preview is rendering the old version of my app no matter how hard the compiler does it's thinking it can grab it from the cache because it existed before and render the preview.
The solution here I think is once a file is removed clear the sandbox file cache so in case the same file gets added back with different content it will show the new version.
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
No files, tests, or entry points are named. First reproduce the sandbox workflow by moving, deleting, and re-adding an HTML file, then trace the file-cache handling; done means the preview uses the new content after a removed file is added again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100