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

chore(deps): update dependency hono to v4 #3

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

chore(deps): update dependency hono to v4 #3

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 12, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
hono (source) ^3.11.11 -> ^4.7.2 age adoption passing confidence

Release Notes

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

New Contributors

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

v4.6.3

Compare Source

This release has many new features, but each feature is small, so we've released it as a patch release.

What's Changed

New Contributors

Full Changelog: honojs/hono@v4.6.2...v4.6.3

v4.6.2

Compare Source

What's Changed

Full Changelog: honojs/hono@v4.6.1...v4.6.2

v4.6.1

Compare Source

What's Changed

New Contributors

Full Changelog: honojs/hono@v4.6.0...v4.6.1

v4.6.0

Compare Source

Hono v4.6.0 is now available!

One of the highlights of this release is the Context Storage Middleware. Let's introduce it.

Context Storage Middleware

Many users may have been waiting for this feature. The Context Storage Middleware uses AsyncLocalStorage to allow handling of the current Context object even outside of handlers.

For example, let’s define a Hono app with a variable message: string.

type Env = {
  Variables: {
    message: string
  }
}

const app = new Hono<Env>()

To enable Context Storage Middleware, register contextStorage() as middleware at the top and set the message value.

import { contextStorage } from 'hono/context-storage'

//...

app.use(contextStorage())

app.use(async (c, next) => {
  c.set('message', 'Hello!')
  await next()
})

getContext() returns the current Context object, allowing you to get the value of the message variable outside the handler.

import { getContext } from 'hono/context-storage'

app.get('/', (c) => {
  return c.text(getMessage())
})

// Access the variable outside the handler.
const getMessage = () => {
  return getContext<Env>().var.message
}

In the case of Cloudflare Workers, you can also access the Bindings outside the handler by using this middleware.

type Env = {
  Bindings: {
    KV: KVNamespace
  }
}

const app = new Hono<Env>()

app.use(contextStorage())

const setKV = (value: string) => {
  return getContext<Env>().env.KV.put('key', value)
}

Thanks @​marceloverdijk !

New features

Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.

@renovate renovate bot force-pushed the renovate/hono-4.x branch 4 times, most recently from da7d23c to bf51a79 Compare February 20, 2024 15:49
@renovate renovate bot force-pushed the renovate/hono-4.x branch 3 times, most recently from 20a5c7b to 8e2f881 Compare February 28, 2024 09:18
@renovate renovate bot force-pushed the renovate/hono-4.x branch 2 times, most recently from 7bcbff3 to a768e6c Compare March 6, 2024 01:19
@renovate renovate bot force-pushed the renovate/hono-4.x branch 2 times, most recently from 1b0cd19 to b0136d3 Compare March 17, 2024 02:10
@renovate renovate bot force-pushed the renovate/hono-4.x branch 3 times, most recently from 594514d to 6290030 Compare March 25, 2024 11:55
@renovate renovate bot force-pushed the renovate/hono-4.x branch 4 times, most recently from 5ae7b14 to cb85986 Compare April 3, 2024 11:21
@renovate renovate bot force-pushed the renovate/hono-4.x branch 2 times, most recently from dcca1bd to f87cac2 Compare April 9, 2024 08:54
@renovate renovate bot force-pushed the renovate/hono-4.x branch 2 times, most recently from ca7da64 to a7e6f8d Compare April 18, 2024 06:52
@renovate renovate bot force-pushed the renovate/hono-4.x branch 3 times, most recently from 9b92482 to ef8e86f Compare April 26, 2024 10:35
@renovate renovate bot force-pushed the renovate/hono-4.x branch 4 times, most recently from 1840836 to 7b45e2f Compare May 5, 2024 02:07
@renovate renovate bot force-pushed the renovate/hono-4.x branch from 7b45e2f to 4295cca Compare May 8, 2024 07:23
@renovate renovate bot force-pushed the renovate/hono-4.x branch 2 times, most recently from 61d8225 to 038d272 Compare August 11, 2024 05:39
@renovate renovate bot force-pushed the renovate/hono-4.x branch 2 times, most recently from 004ada7 to b817318 Compare August 22, 2024 20:57
@renovate renovate bot force-pushed the renovate/hono-4.x branch 2 times, most recently from 4b3a859 to 40379dd Compare August 31, 2024 08:42
@renovate renovate bot force-pushed the renovate/hono-4.x branch from 40379dd to 43bbb59 Compare September 4, 2024 20:43
@renovate renovate bot force-pushed the renovate/hono-4.x branch from 43bbb59 to 041c7da Compare September 17, 2024 02:29
@renovate renovate bot force-pushed the renovate/hono-4.x branch from 041c7da to 7850db3 Compare September 25, 2024 02:59
@renovate renovate bot force-pushed the renovate/hono-4.x branch 2 times, most recently from aafd1c6 to 6f1c5cd Compare October 18, 2024 02:44
@renovate renovate bot force-pushed the renovate/hono-4.x branch 2 times, most recently from b8cd3ad to da2ad9b Compare October 26, 2024 05:17
@renovate renovate bot force-pushed the renovate/hono-4.x branch 2 times, most recently from fee9033 to 8d50fce Compare November 5, 2024 02:30
@renovate renovate bot force-pushed the renovate/hono-4.x branch from 8d50fce to 8a8d681 Compare November 13, 2024 23:27
@renovate renovate bot force-pushed the renovate/hono-4.x branch 2 times, most recently from 28a8f91 to 657c93d Compare November 25, 2024 20:48
@renovate renovate bot force-pushed the renovate/hono-4.x branch from 657c93d to 36cd364 Compare December 6, 2024 20:57
@renovate renovate bot force-pushed the renovate/hono-4.x branch from 36cd364 to 1a1ad48 Compare December 15, 2024 02:51
@renovate renovate bot force-pushed the renovate/hono-4.x branch from 1a1ad48 to 6c7003d Compare December 28, 2024 20:36
@renovate renovate bot force-pushed the renovate/hono-4.x branch from 6c7003d to c2f221f Compare January 7, 2025 07:19
@renovate renovate bot force-pushed the renovate/hono-4.x branch 3 times, most recently from 1b46dcf to 6f64a8c Compare January 26, 2025 11:34
@renovate renovate bot force-pushed the renovate/hono-4.x branch 2 times, most recently from 22de8c1 to 33f183e Compare February 7, 2025 08:20
@renovate renovate bot force-pushed the renovate/hono-4.x branch from 33f183e to 034deda Compare February 14, 2025 08:05
@renovate renovate bot force-pushed the renovate/hono-4.x branch from 034deda to 26697cd Compare February 19, 2025 23:53
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
None yet
Projects
None yet
Milestone
No milestone
Development

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