Skip to content
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.

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

fix(deps): update dependency hono to v4.7.5 #147

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 28, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
hono (source) 4.6.14 -> 4.7.5 age adoption passing confidence

Release Notes

honojs/hono (hono)

v4.7.5

Compare Source

v4.7.4

Compare Source

What's Changed

Full Changelog: honojs/hono@v4.7.3...v4.7.4

v4.7.3

Compare Source

What's Changed
New Contributors

Full Changelog: honojs/hono@v4.7.2...v4.7.3

v4.7.2

Compare Source

What's Changed

Full Changelog: honojs/hono@v4.7.1...v4.7.2

v4.7.1

Compare Source

What's Changed
New Contributors

Full Changelog: honojs/hono@v4.7.0...v4.7.1

v4.7.0

Compare Source

Release Notes

Hono v4.7.0 is now available!

This release introduces one helper and two middleware.

  • Proxy Helper
  • Language Middleware
  • JWK Auth Middleware

Plus, Standard Schema Validator has been born.

Let's look at each of these.

Proxy Helper

We sometimes use the Hono application as a reverse proxy. In that case, it accesses the backend using fetch. However, it sends an unintended headers.

app.all('/proxy/:path', (c) => {
  // Send unintended header values to the origin server
  return fetch(`http://${originServer}/${c.req.param('path')}`)
})

For example, fetch may send Accept-Encoding, causing the origin server to return a compressed response. Some runtimes automatically decode it, leading to a Content-Length mismatch and potential client-side errors.

Also, you should probably remove some of the headers sent from the origin server, such as Transfer-Encoding.

Proxy Helper will send requests to the origin and handle responses properly. The above headers problem is solved simply by writing as follows.

import { Hono } from 'hono'
import { proxy } from 'hono/proxy'

app.get('/proxy/:path', (c) => {
  return proxy(`http://${originServer}/${c.req.param('path')}`)
})

You can also use it in more complex ways.

app.get('/proxy/:path', async (c) => {
  const res = await proxy(
    `http://${originServer}/${c.req.param('path')}`,
    {
      headers: {
        ...c.req.header(),
        'X-Forwarded-For': '127.0.0.1',
        'X-Forwarded-Host': c.req.header('host'),
        Authorization: undefined,
      },
    }
  )
  res.headers.delete('Set-Cookie')
  return res
})

Thanks @​usualoma!

Language Middleware

Language Middleware provides 18n functions to Hono applications. By using the languageDetector function, you can get the language that your application should support.

import { Hono } from 'hono'
import { languageDetector } from 'hono/language'

const app = new Hono()

app.use(
  languageDetector({
    supportedLanguages: ['en', 'ar', 'ja'], // Must include fallback
    fallbackLanguage: 'en', // Required
  })
)

app.get('/', (c) => {
  const lang = c.get('language')
  return c.text(`Hello! Your language is ${lang}`)
})

You can get the target language in various ways, not just by using Accept-Language.

  • Query parameters
  • Cookies
  • Accept-Language header
  • URL path

Thanks @​lord007tn!

JWK Auth Middleware

Finally, middleware that supports JWK (JSON Web Key) has landed. Using JWK Auth Middleware, you can authenticate by verifying JWK tokens. It can access keys fetched from the specified URL.

import { Hono } from 'hono'
import { jwk } from 'hono/jwk'

app.use(
  '/auth/*',
  jwk({
    jwks_uri: `https://${backendServer}/.well-known/jwks.json`,
  })
)

app.get('/auth/page', (c) => {
  return c.text('You are authorized')
})

Thanks @​Beyondo!

Standard Schema Validator

Standard Schema provides a common interface for TypeScript validator libraries. Standard Schema Validator is a validator that uses it. This means that Standard Schema Validator can handle several validators, such as Zod, Valibot, and ArkType, with the same interface.

The code below really works!

import { Hono } from 'hono'
import { sValidator } from '@​hono/standard-validator'
import { type } from 'arktype'
import * as v from 'valibot'
import { z } from 'zod'

const aSchema = type({
  agent: 'string',
})

const vSchema = v.object({
  slag: v.string(),
})

const zSchema = z.object({
  name: z.string(),
})

const app = new Hono()

app.get(
  '/:slag',
  sValidator('header', aSchema),
  sValidator('param', vSchema),
  sValidator('query', zSchema),
  (c) => {
    const headerValue = c.req.valid('header')
    const paramValue = c.req.valid('param')
    const queryValue = c.req.valid('query')
    return c.json({ headerValue, paramValue, queryValue })
  }
)

const res = await app.request('/foo?name=foo', {
  headers: {
    agent: 'foo',
  },
})

console.log(await res.json())

Thanks @​muningis!

New features
All changes
New Contributors

Full Changelog: honojs/hono@v4.6.20...v4.7.0

v4.6.20

Compare Source

What's Changed
New Contributors

Full Changelog: honojs/hono@v4.6.19...v4.6.20

v4.6.19

Compare Source

What's Changed

Full Changelog: honojs/hono@v4.6.18...v4.6.19

v4.6.18

Compare Source

What's Changed

Full Changelog: honojs/hono@v4.6.17...v4.6.18

v4.6.17

Compare Source

What's Changed
New Contributors

Full Changelog: honojs/hono@v4.6.16...v4.6.17

v4.6.16

Compare Source

What's Changed

Full Changelog: honojs/hono@v4.6.15...v4.6.16

v4.6.15

Compare Source

c.json() etc. throwing type error when the status is contentless code, e.g., 204

From this release, when c.json(), c.text(), or c.html() returns content, specifying a contentless status code such as 204 will now throw a type error.

CleanShot 2024-12-28 at 16 47 39@​2x

At first glance, this seems like a breaking change but not. It is not possible to return a contentless response with c.json() or c.text(). So, in that case, please use c.body().

app.get('/', (c) => {
  return c.body(null, 204)
})
What's Changed
New Contributors

Full Changelog: honojs/hono@v4.6.14...v4.6.15


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

Copy link

changeset-bot bot commented Dec 28, 2024

⚠️ No Changeset found

Latest commit: 743155a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate renovate bot changed the title fix(deps): update dependency hono to v4.6.15 fix(deps): update dependency hono to v4.6.16 Jan 5, 2025
@renovate renovate bot changed the title fix(deps): update dependency hono to v4.6.16 fix(deps): update dependency hono to v4.6.17 Jan 18, 2025
@renovate renovate bot force-pushed the renovate/hono-4.x-lockfile branch from 692d77a to cd1f9ed Compare January 18, 2025 09:25
@renovate renovate bot changed the title fix(deps): update dependency hono to v4.6.17 fix(deps): update dependency hono to v4.6.18 Jan 23, 2025
@renovate renovate bot force-pushed the renovate/hono-4.x-lockfile branch 2 times, most recently from 271f877 to 200b8a4 Compare January 26, 2025 10:24
@renovate renovate bot changed the title fix(deps): update dependency hono to v4.6.18 fix(deps): update dependency hono to v4.6.19 Jan 26, 2025
@renovate renovate bot force-pushed the renovate/hono-4.x-lockfile branch from 200b8a4 to 1088163 Compare January 31, 2025 06:44
@renovate renovate bot changed the title fix(deps): update dependency hono to v4.6.19 fix(deps): update dependency hono to v4.6.20 Jan 31, 2025
@renovate renovate bot force-pushed the renovate/hono-4.x-lockfile branch from 1088163 to 9add45d Compare February 7, 2025 06:39
@renovate renovate bot changed the title fix(deps): update dependency hono to v4.6.20 fix(deps): update dependency hono to v4.7.0 Feb 7, 2025
@renovate renovate bot changed the title fix(deps): update dependency hono to v4.7.0 fix(deps): update dependency hono to v4.7.1 Feb 13, 2025
@renovate renovate bot force-pushed the renovate/hono-4.x-lockfile branch from 9add45d to a35314e Compare February 13, 2025 13:56
@renovate renovate bot changed the title fix(deps): update dependency hono to v4.7.1 fix(deps): update dependency hono to v4.7.2 Feb 19, 2025
@renovate renovate bot force-pushed the renovate/hono-4.x-lockfile branch from a35314e to 516e733 Compare February 19, 2025 00:41
@renovate renovate bot force-pushed the renovate/hono-4.x-lockfile branch 2 times, most recently from 47a5f4a to bd81257 Compare March 5, 2025 05:04
@renovate renovate bot changed the title fix(deps): update dependency hono to v4.7.2 fix(deps): update dependency hono to v4.7.4 Mar 5, 2025
@renovate renovate bot changed the title fix(deps): update dependency hono to v4.7.4 fix(deps): update dependency hono to v4.7.5 Mar 20, 2025
@renovate renovate bot force-pushed the renovate/hono-4.x-lockfile branch from bd81257 to 743155a Compare March 20, 2025 09:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants