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.

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 hono #1560

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

fix(deps): update hono #1560

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 11, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@hono/node-server ^1.12.2 -> ^1.13.8 age adoption passing confidence
@hono/zod-validator ^0.2.2 -> ^0.4.3 age adoption passing confidence
hono (source) ^4.5.11 -> ^4.7.2 age adoption passing confidence

Release Notes

honojs/node-server (@​hono/node-server)

v1.13.8

Compare Source

What's Changed

New Contributors

Full Changelog: honojs/node-server@v1.13.7...v1.13.8

v1.13.7

Compare Source

What's Changed

New Contributors

Full Changelog: honojs/node-server@v1.13.6...v1.13.7

v1.13.6

Compare Source

What's Changed

Full Changelog: honojs/node-server@v1.13.5...v1.13.6

v1.13.5

Compare Source

What's Changed

Full Changelog: honojs/node-server@v1.13.4...v1.13.5

v1.13.4

Compare Source

What's Changed
New Contributors

Full Changelog: honojs/node-server@v1.13.3...v1.13.4

v1.13.3

Compare Source

What's Changed

New Contributors

Full Changelog: honojs/node-server@v1.13.2...v1.13.3

v1.13.2

Compare Source

What's Changed

New Contributors

Full Changelog: honojs/node-server@v1.13.1...v1.13.2

v1.13.1

Compare Source

What's Changed

Full Changelog: honojs/node-server@v1.13.0...v1.13.1

v1.13.0

Compare Source

What's Changed

Full Changelog: honojs/node-server@v1.12.2...v1.13.0

honojs/middleware (@​hono/zod-validator)

v0.4.3

Compare Source

Patch Changes

v0.4.2

Compare Source

Patch Changes

v0.4.1

Compare Source

Patch Changes

v0.3.0

Compare Source

Minor Changes
honojs/hono (hono)

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

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

v4.6.6

Compare Source

What's Changed

New Contributors

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

v4.6.5

Compare Source

Security fix for CSRF Protection Middleware

This release includes a security fix for CSRF Protection Middleware. If you are using CSRF Protection Middleware, please upgrade this hono package immediately.

Before this release, a request without a Content-Type header can bypass the protection. This fix does not allow it. See: GHSA-2234-fmw7-43wr

What's Changed

New Contributors

Full Changelog: honojs/hono@v4.6.4...v4.6.5

v4.6.4

Compare Source

What's Changed

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

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

@renovate renovate bot added the renovate label Sep 11, 2024
@renovate renovate bot changed the title fix(deps): update dependency hono to ^4.6.0 fix(deps): update dependency hono to ^4.6.1 Sep 11, 2024
@renovate renovate bot changed the title fix(deps): update dependency hono to ^4.6.1 fix(deps): update hono Sep 16, 2024
@renovate renovate bot force-pushed the renovate/hono branch 2 times, most recently from 1f0f85c to 2480ef8 Compare September 21, 2024 14:11
@renovate renovate bot force-pushed the renovate/hono branch 2 times, most recently from efa12c3 to 8e8cf26 Compare September 26, 2024 04:29
@renovate renovate bot force-pushed the renovate/hono branch 2 times, most recently from 6f50451 to 8177332 Compare October 6, 2024 07:32
@renovate renovate bot force-pushed the renovate/hono branch 3 times, most recently from 04de2a3 to d928c4f Compare October 15, 2024 10:02
@renovate renovate bot force-pushed the renovate/hono branch 3 times, most recently from 539f322 to 4ea3d8b Compare October 28, 2024 07:13
@renovate renovate bot force-pushed the renovate/hono branch 4 times, most recently from e3ad9fa to a90ddbe Compare November 4, 2024 06:54
@renovate renovate bot force-pushed the renovate/hono branch 3 times, most recently from 61ac9e6 to cf9d884 Compare November 13, 2024 11:28
@renovate renovate bot force-pushed the renovate/hono branch 2 times, most recently from a3b0d5a to 39dde61 Compare November 25, 2024 08:41
@renovate renovate bot force-pushed the renovate/hono branch 3 times, most recently from 06fb522 to 1640f72 Compare December 20, 2024 08:42
@renovate renovate bot force-pushed the renovate/hono branch 3 times, most recently from c2764ab to 64fac55 Compare January 5, 2025 10:36
@renovate renovate bot force-pushed the renovate/hono branch 2 times, most recently from 3184832 to 660bcaa Compare January 18, 2025 09:53
@renovate renovate bot force-pushed the renovate/hono branch 2 times, most recently from f08c5ff to c47ced3 Compare January 26, 2025 11:03
@renovate renovate bot force-pushed the renovate/hono branch 2 times, most recently from 21fd46b to 6b96a93 Compare January 31, 2025 11:13
@renovate renovate bot force-pushed the renovate/hono branch 2 times, most recently from 562f7ff to 2e69298 Compare February 13, 2025 09:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
renovate
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants