Hopefully, the random file names generated by the package to avoid caching problems
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 511
- Forks
- 83
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 55
Description
Our packaged file name has always been Component-preload.js and manifest.json, so each deployment has caching problems, if you keep disabling the cache, and will affect the user experience! Can you package the production name is random, so you can avoid caching problems, or we configure NG only index.html no cache on it.
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
Start by reviewing the packaging behavior that produces Component-preload.js and manifest.json. Determine whether the intended solution is randomized production filenames or a no-cache rule for index.html, then verify that deployments no longer reuse stale packaged assets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100