max-mapper / max-mapper/requirebin
Stuck with old version of a package
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 389
- Forks
- 73
- PR merge metrics
- No merged PRs in 30d
Description
My browsers seem to be stuck with an old version of a required package.
Using private browsing mode works around it.
Where is it cached?
Is this really what is going on?
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 issue names no files, tests, or entry points. Reproduce the stale required-package behavior in a normal browser and private browsing mode, then trace the package-loading and caching path; done means the cause is confirmed and a concrete fix or follow-up is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100