New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix(deps): update dependency itty-router to v5 #44

Open

renovate wants to merge 1 commit into main from renovate/itty-router-5.x

Contributor

renovate bot commented Apr 30, 2024 •

edited

Loading

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
itty-router (source)	`2.6.6` -> `5.0.18`

Release Notes

kwhitley/itty-router (itty-router)

`v5.0.18`

See v5.0.18 CHANGELOG entry for notes

`v5.0.17`

fixed: corsify should clone response before appending headers

`v5.0.16`

maintenance: README

`v5.0.15`

maintenance: types cleanup and publishing test

`v5.0.14`

maintenance: types cleanup and publishing test

`v5.0.13`

fixed: Router/AutoRouter stages were not connected to router-level generics

`v5.0.12`

fixed: ./types was not being properly exported

`v5.0.11`

`v5.0.10`

fixed: response formatters in finally stage could still cross pollute headers in Node

`v5.0.9`

fixed: cors preflight should reflect requested headers as the default (required for credentials)

`v5.0.8`

`v5.0.7`

fixed: withParams could attempt to bind null (collision with node adapter)

`v5.0.6`

fixed: corsify as replacing status codes (now mutates original response)

`v5.0.5`

fixed: corsify now properly ignores WebSocket responses

`v5.0.4`

fixed: (TypeScript) middleware corrupting downstream request types and args

`v5.0.3`

`v5.0.2`

fixed: AutoRouter was missing the router-level generics support of the other 2 routers.
- fixed: All 3 routers had their 3rd generic argument, ResponseType added per the spec.

`v5.0.1`

fixed: corsify should clone response before appending headers

`v5.0.0`

BREAKING: router.fetch replaces router.handle (now deprecated)
- BREAKING: "createCors" has been deprecated in favor of "cors" (new options & requirements)
- changed: previous Router (smallest) is now IttyRouter
- added: Router (full backwards compatability with previous Router) has been added, including:
  - "before" stage (array of request handlers)
  - "finally" stage (array of response handlers)
  - "catch" stage (single error handler)
- added: AutoRouter (batteries-included Router)
- fixed (TS): Routers types have been modified to allow both rotuer-level generics AND route-level generics in the same instance.
- docs: see Migration guide at https://itty.dev/itty-router/migrations/v4-v5

For changes prior to v5, see the v4 CHANGELOG

`v4.2.2`

`v4.2.1`

`v4.2.0`

`v4.1.1`

`v4.1.0`

`v4.0.28`

`v4.0.27`

`v4.0.26`

`v4.0.25`

`v4.0.24`

`v4.0.23`

`v4.0.22`

`v4.0.21`

`v4.0.20`

`v4.0.19`

`v4.0.18`

`v4.0.17`

`v4.0.16`

`v4.0.15`

`v4.0.14`

`v4.0.13`

`v4.0.12`

`v4.0.11`

`v4.0.10`

`v4.0.9`

`v4.0.8`

`v4.0.7`

`v4.0.6`

`v4.0.5`

`v4.0.4`

`v4.0.3`

`v4.0.2`

`v4.0.1`

`v4.0.0`

This is an extensive v4.x update, bringing a series of quality of life additions, as well as a potentially breaking change for TypeScript users:

!Breaking Changes!

TYPES HAVE CHANGED FOR THE ROUTER. The core TypeScript and exposed types for the Router itself have been completely retooled to allow much better, strong type support throughout your routes. Previously this required complex custom setups to work around the lack of internal typing. Now it's included out of the box, but you'll need to follow the instructions.

This was not an easy change to commit to, but was long overdue. The solution finally settled on allows for a more flexible (yet boiler-platey) approach, or a more rigid one... but allows for many more scenarios than the previous types did.

Other Changes

added: nearly all the extras from itty-router-extras have moved in-house to the core library. This library will be deprecated as a result.
added: createCors from itty-cors has moved into the core library as well
feature: withParams middleware (previously from itty-router-extras) is now possible to use as upstream middleware (e.g. globally) to reduce boilerplate. Previously this was not possible.

Official Documentation Site

We've just launched a itty.dev to house documentation for all the itty projects going forward. Previously, we auto-generated docs from the README, but clearly the documentation needs far outweighed what could feasibly fit within a single long README. See the itty-router section for more details!

See the migration guide for complete details.

`v3.0.12`

`v3.0.11`

`v3.0.10`

`v3.0.9`

`v3.0.8`

`v3.0.7`

`v3.0.6`

`v3.0.5`

`v3.0.4`

`v3.0.3`

`v3.0.2`

`v3.0.1`

Configuration

📅 Schedule: Branch creation - "* 0-3 1 * *" in timezone Asia/Singapore, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

ngshiheng force-pushed the main branch from c532d54 to 3e99f76 Compare

July 10, 2024 11:41


          fix(deps): update dependency itty-router to v5

01721cf

renovate bot force-pushed the renovate/itty-router-5.x branch from 0b459ad to 01721cf Compare

August 16, 2024 18:13

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet