topbit 3.0.0 → 3.0.1

package/README.cn.md

@@ -131,7 +131,7 @@ GET POST PUT PATCH DELETE OPTIONS  TRACE HEAD
 
 'use strict'
 
-const Topbit = require('titibit')
+const Topbit = require('topibit')
 
 const app = new Topbit({
   debug: true
@@ -705,14 +705,12 @@ app.use(async (c, next) => {
 })
 
 //use可以级联: app.use(m1).use(m2)
-//在21.5.4版本以后，不过这个功能其实根本不重要
-//因为有topbit-loader扩展，实现的功能要强大的多。
 
 ```
 
 ## topbit完整的流程图示
 
-![](images/topbit-middleware.png)
+![](images/topbit-middleware.webp)
 
 
 > **需要知道的是，其实在内部，body数据接收和解析也都是中间件，只是刻意安排了顺序，分出了pre和use接口。**

package/README.md

@@ -113,7 +113,7 @@ The first 6 are the most commonly used. For each request type, the router has a
 
 'use strict'
 
-const Topbit = require('titibit')
+const Topbit = require('topibit')
 
 const app = new Topbit({
   debug: true
@@ -678,13 +678,11 @@ app.use(async (c, next) => {
 })
 
 // use can be cascaded: app.use(m1).use(m2)
-// Available after v21.5.4, but this feature is not critical
-// because the topbit-loader extension offers much more powerful functionality.
 ```
 
 ## Topbit Complete Flow Chart
 
-![](images/topbit-middleware.png)
+![](images/topbit-middleware.webp)
 
 > **It is important to know that internally, body data reception and parsing are also middleware. The order is deliberately arranged, separating `pre` and `use` interfaces.**
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "topbit",
-  "version": "3.0.0",
+  "version": "3.0.1",
   "description": "A Server-side web framework support http/1.1 and http/2",
   "main": "src/topbit.js",
   "directories": {