Planning for koa-static-cache v6 — Feedback, Ideas & Roadmap

[iietmoon]

🎯 Goal

Plan, track, and discuss upcoming changes for version 6.0 of koa-static-cache.

The library still serves many Koa users with local and small-scale static serving needs. This version aims to modernize the codebase, improve developer experience, and expand flexibility by optionally integrating with external CDNs like Amazon S3 — all while keeping the core functionality of serving local static assets intact.

---

✅ What will stay

• Static file serving from local disk
• Optional in-memory (buffer) caching
• Gzip & precompiled gzip support
• File aliasing
• Preload and dynamic modes
• MD5-based ETag handling

---

🔧 Planned changes

• Drop support for Node.js < 14
• Add optional CDN support (S3 or custom provider)
• Convert to modern JavaScript (ESM or discuss keeping CJS)
• Add TypeScript types or migrate fully to TypeScript
• Improve logging and debug visibility
• Refactor internals for better maintainability and flexibility
• Add additional tests and edge case coverage
• Consider support for HTTP Range requests (TBD)
• Update and audit dependencies

---

💥 Potential Breaking Changes

• Dropping support for old Node.js versions
• Internal structure or exported API changes
• Changes to default caching behavior (with migration paths)

---

🌐 New Features Discussion

• CDN mode (optional): fallback or primary static asset resolution from S3 (or other providers), allowing hybrid disk + cloud strategies.
• Configurable provider interface (so others can write adapters, e.g., Cloudflare R2, Backblaze B2, etc.)
• Support signed URLs / cache strategies when using remote sources (TBD)

---

🗣️ Feedback welcome!

If you’re a koa-static-cache user, we’d love to hear from you:

• What works well today?
• What do you wish this middleware did better?
• Would CDN support help your use case?
• Anything that’s been a pain point with the current version?