feat: replace cache-content-type with mime-types directly by 3imed-jaberi · Pull Request #1886 · koajs/koa (original) (raw)

@3imed-jaberi

Checklist

@codecov

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.90%. Comparing base (2f6e814) to head (40d41e6).
Report is 1 commits behind head on master.

Additional details and impacted files

@@ Coverage Diff @@ ## master #1886 +/- ##

Coverage 99.90% 99.90%

Files 9 9
Lines 2046 2048 +2

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

@3imed-jaberi

@jonathanong I’ve removed cache-content-type because it’s not in sync with the latest mime-types. I think we should rely directly on the upstream mime-types package instead. If you’re on board, we can move forward with this PR. Otherwise, happy to close it!

@jonathanong

@fengmk2 @dead-horse why do we need to cache the content type? I think all the mime types are already in memory

@3imed-jaberi

@jonathanong

@3imed-jaberi my preference would be to just remove caching entirely

@3imed-jaberi

@3imed-jaberi 3imed-jaberi changed the titlefeat: replcae cache-content-type with mime-types directly (keeps ylru cache) feat: replace cache-content-type with mime-types directly

Jun 5, 2025

@3imed-jaberi

@fengmk2

Cache is no longer needed +1

jonathanong

@3imed-jaberi 3imed-jaberi deleted the replace-cache-content-type-with-mime-type-direct branch

June 6, 2025 12:11

This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters

[ Show hidden characters]({{ revealButtonHref }})