Conversation
* feat: enable cacheImmutable by default * fix: thoses files shouldn't immutable * fix: update cache control logic becauses undefined !== false (true) * test: add tests for cacheControl option behavior with cacheImmutable set to false * refactor: normalize cacheControl handling in response headers * refactor: simplify maxAge calculation in cacheControl handling
…ned` when not found
…ddleware (#2259) * feat: add `forwardError` option to enable error forwarding to next middleware * feat: add error middleware support in frameworkFactory for improved error handling * feat: enhance error handling by removing response headers before forwarding errors * feat: remove error middleware option from frameworkFactory for cleaner middleware setup * test: update middleware tests to reflect changes in error handling with forwardError option * test: update middleware tests to handle error forwarding for hapi framework * feat: implement error forwarding in koa middleware and update tests accordingly * feat: add error forwarding support in hono middleware and update tests accordingly * feat: add forwardError option to README with usage example
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2284 +/- ##
==========================================
+ Coverage 95.88% 96.11% +0.22%
==========================================
Files 13 3 -10
Lines 900 900
Branches 270 266 -4
==========================================
+ Hits 863 865 +2
+ Misses 37 35 -2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Sometimes |
|
@bjohansebas I will make a webpack-cli release and focus on it, there are three things left:
I will take care about them, so you can focus on webpack-dev-server more |
|
Okay, but for compile.validate, we need webpack to release that support. The PR was already merged in webpack, but it’s not officially published on npm yet, so it can’t be updated yet to include that support |
|
@bjohansebas Yeah, I just want to add this check for future |
alexander-akait
force-pushed
the
next
branch
2 times, most recently
from
8857ef1 to
ddc1b52
Compare
alexander-akait
force-pushed
the
next
branch
2 times, most recently
from
16e933b to
2454301
Compare
alexander-akait
force-pushed
the
next
branch
2 times, most recently
from
efea91e to
38aed91
Compare
|
Looks like known issue - honojs/node-server#233 |
🦋 Changeset detectedLatest commit: 060bb9a The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
2 participants
Summary
No squash when merging
What kind of change does this PR introduce?
Did you add tests for your changes?
Does this PR introduce a breaking change?
If relevant, what needs to be documented once your changes are merged or what have you already documented?
Use of AI