c608fa9532
* feat(zod-openapi): create swagger-ui jsx component * feat(zod-openapi): add swagger ui docs * chore(zod-openapi): add versioning doc * chore(zod-openapi): fix SwaggerUI component doc * refactor(zod-openapi): remove jsx comment * feat(swagger-ui): create new package * feat(swagger-ui): provides swagger ui middleware and swaggerui component * feat(zod-openapi): Changed to use @hono/swagger-ui * chore: add versioning doc * feat: update ci for @hono/swagger-ui * refactor: remove package-lock.json * refactor: reverted the extra changes. * chore: remove old changeset doc * refactor(swagger-ui): remove unused file * refactor(swagger-ui): change input type * feat(swagger-ui): Select only the options you need. * chore(swagger-ui): update README * refactor(swagger-ui): rewrite simple * refactor(zod-openapi): remove swagger-ui * chore(swagger-ui): fix readme content * chore(dep): add @types/swagger-ui-dist for option types support * feat: implement SwaggerConfig Renderer for mapping config object to html * feat: extend some option support for swagger-ui-dist * test: move option rendering test and add some cases * feat: add manually option for making full customizable * docs: update swagger-ui middleware README * fix: do not escape HTML strings * docs: update README of swagger-ui middleware * ci: update workflow environment for swagger-ui middleware --------- Co-authored-by: naporin0624 <naporin0624@gmail.com> |
||
|---|---|---|
| .changeset | ||
| .github/workflows | ||
| .vscode | ||
| packages | ||
| .eslintignore | ||
| .eslintrc.js | ||
| .gitignore | ||
| .prettierrc | ||
| README.md | ||
| jest.config.js | ||
| package.json | ||
| tsconfig.json | ||
| yarn.lock | ||
README.md
monorepo for Hono third-party middleware
This repository is monorepo for third-party middleware of Hono. We develop middleware in this repository and manage the issues and pull requests.
What is third-party middleware?
Hono has three types of middleware.
- Custom middleware - Created by users themselves.
- Built-in middleware - Included in the Hono core package. It does not depend on any other external libraries.
- Third-party middleware - Created outside of the core package. It can depend on the external libraries.
Third-party middleware is maintained in this github.com/honojs/middleware repository and published to npm in the @hono namespace. For example, a third-party middleware called hello is hosted at github.com/honojs/middleware/packages/hello and distributed under the name @hono/hello.
You can install it with the following command.
npm install @hono/hello
For Deno, we do not publish them on deno.land/x, but distribute them via CDNs such as Skypack and esm.sh. We will also use the npm: that will be introduced in the Deno itself in the future.
import { hello } from 'npm:@hono/hello'
How to contribute
Anyone can propose third-party Middleware. The Hono maintainers and other contributors will discuss whether we accept the middleware or not. If it's OK, it will be maintained in this repository. The proposer maintains it.
The specific flow is as follows
- Clone this repository
- Write your middleware. Refer to hello Middleware.
- Create the pull request.
We use changesets to manage releases and CHANGELOG. Run the following command at the top level to describe any changes.
yarn changeset
When merged into the main, a pull request for release is created. The Hono maintainers will merge it to release the package at the appropriate time.
Author & License
The Author of this repository is Yusuke Wada <https://github.com/yusukebe>. However, the code under the packges/* is in each Middleware author.
Basically, distributed under the MIT license.