V1 Rewrite

[hoangvvo]

This is the rewrite of next-connect. There are many breaking changes. See README.md for more detail.

The motivation of this rewrite is to:

• provide a more stable/straight-forward implementation. avoid this hacky solution. Now the handler will resolve based on pure promise resolution.
• new async paradigm like Koa for more flexibility. Close Support async middleware chains #146, Close Running a handler at the end of chain?  #170, Close Handle error in getServerSideProps #184.
• correct some behaviors.
  • in handler(), if there is no matching .method() (even if there are matchign .use()`, nothing should be executed. close how to order the response [onNoMatch] #188.
  • onError should also be triggered when throwing in onNoMatch. close Handling errors that are thrown in onNoMatch handler #65
• forward returned value from handlers, which enables some interesting use cases. close redirecting in getServerSideProps middleware #194
• Move to named export to avoid some issues with bundler. Close Cannot access '__WEBPACK_DEFAULT_EXPORT__' before initialization #189. We also have full support for ESM/CJS
• Supports Edge Runtime, Edge API Routes, Middleware. The agnostic router allows us to implement this easily. (will be done in a separate pr)

With this, we will be heading for 1.0! 0.x version will still be supported (I am planning to make some semi-breaking changes to correct some behaviors, esp. the two in the last bullet point above, as well as fixing some bugs) Close #126

Check out the example: https://github.com/hoangvvo/next-connect/tree/v1-rewrite/examples/nextjs

[changeset-bot]

⚠️ No Changeset found

Latest commit: 9581197

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[merlindru]

Awesome!!! Thank you for your hard work! 🙂

What's required to get this landed?

Could we get an npm release? npm i next-connect@next or @beta would be cool!

[hoangvvo]

Awesome!!! Thank you for your hard work! slightly_smiling_face

What's required to get this landed?

Could we get an npm release? npm i next-connect@next or @beta would be cool!

This should be landing soon 🚀

[codecov]

Codecov Report

Merging #196 (9581197) into main (e55318a) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##              main      #196    +/-   ##
==========================================
  Coverage   100.00%   100.00%            
==========================================
  Files            1         3     +2     
  Lines           86       248   +162     
  Branches         0        43    +43     
==========================================
+ Hits            86       248   +162     

Impacted Files	Coverage Δ
src/index.ts	100.00% <100.00%> (ø)
src/node.ts	100.00% <100.00%> (ø)
src/router.ts	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e55318a...9581197. Read the comment docs.

[hoangvvo]

Published as next!

npm i next-connect@next