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.1 #331

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 11, 2024

This PR contains the following updates:

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

Release Notes

honojs/hono (hono)

v4.7.1

Compare Source

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

v4.6.14

Compare Source

What's Changed

New Contributors

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

v4.6.13

Compare Source

What's Changed

New Contributors

Full Changelog: honojs/hono@v4.6.12...v4.6.13

v4.6.12

Compare Source

What's Changed

New Contributors

Full Changelog: honojs/hono@v4.6.11...v4.6.12

v4.6.11

Compare Source

What's Changed

New Contributors

Full Changelog: honojs/hono@v4.6.10...v4.6.11

v4.6.10

Compare Source

What's Changed

New Contributors

Full Changelog: honojs/hono@v4.6.9...v4.6.10

v4.6.9

Compare Source

What's Changed
New Contributors

Full Changelog: honojs/hono@v4.6.8...v4.6.9

v4.6.8

Compare Source

What's Changed

New Contributors

Full Changelog: honojs/hono@v4.6.7...v4.6.8

v4.6.7

Compare Source

What's Changed

New Contributors

Full Changelog: honojs/hono@v4.6.6...v4.6.7


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

Copy link

github-actions bot commented Nov 11, 2024

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name Status Preview Last Commit
enclosed ✅ Ready (View Log) Visit Preview 7c5a8d6
enclosed-docs ✅ Ready (View Log) Visit Preview 7c5a8d6

@renovate renovate bot changed the title fix(deps): update dependency hono to v4.6.9 fix(deps): update dependency hono to v4.6.10 Nov 13, 2024
@renovate renovate bot changed the title fix(deps): update dependency hono to v4.6.10 fix(deps): update dependency hono to v4.6.11 Nov 20, 2024
@renovate renovate bot changed the title fix(deps): update dependency hono to v4.6.11 fix(deps): update dependency hono to v4.6.12 Nov 25, 2024
@renovate renovate bot changed the title fix(deps): update dependency hono to v4.6.12 fix(deps): update dependency hono to v4.6.13 Dec 6, 2024
@renovate renovate bot changed the title fix(deps): update dependency hono to v4.6.13 fix(deps): update dependency hono to v4.6.14 Dec 14, 2024
@renovate renovate bot changed the title fix(deps): update dependency hono to v4.6.14 fix(deps): update dependency hono to v4.6.15 Dec 28, 2024
@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 force-pushed the renovate/hono-4.x-lockfile branch from 3fcf3b0 to 1380e3b Compare January 18, 2025 13:04
@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 1380e3b to 4a6f5da Compare January 23, 2025 13:18
@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 from 4a6f5da to 8e0c871 Compare January 26, 2025 10:19
@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 8e0c871 to a24a4ec Compare January 27, 2025 19:43
@renovate renovate bot force-pushed the renovate/hono-4.x-lockfile branch from a24a4ec to 241719e Compare January 30, 2025 17:21
@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 2ea0d1a to 7c5a8d6 Compare February 13, 2025 10:14
@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
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