v5.0.0 Major Release Proposal
See original GitHub issueLet’s discuss changes for koa-body v5.0.0. These are the items that I’d like to see rolled into the next release.
- Update
co-body
to 6.0.0 - Modernize
koa-body
codebase (#136, #213) - Add linting, coverage, and benchmarks (#136, #213)
- Remove
strict
option (#137) - Rework options
- Remove
patchNode
andpatchKoa
options ❓ - Cleaner limits options
- Remove
- Make
onError
more predictable (#112) - Drop support for Node.js 6
- Start testing on Node.js 12
- Parse bodies on DELETE by default (#163)
I think we’ll target late April or early May for this release assuming maintainers and contributors have enough time.
I’m looking forward to hearing thoughts and feedback on this list. 👋
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:15 (13 by maintainers)
Top Results From Across the Web
Release new major v5.0.0 · Issue #550 · Level/leveldown
Just making an issue for this for referencing other ongoing work. We will release some rc's first and once we have released v5.0.0...
Read more >v5 Release Notes | Documentation - ServiceStack Docs
Enhancement Releases The {MAJOR} is reserved for Major releases like v5 containing structural changes that may require changes to environment and/or project ...
Read more >Node v5.0.0 (Current)
This new version of Node.js, however, will only be supported for 8 months, with a new major version, v6, being released in April...
Read more >Versions - FHIR v5.0.0-snapshot3 - HL7 FHIR Specification
The next major publication of FHIR will be Release 5. It is our hope release 5 will include more Normative content, including more...
Read more >Version v5.0.0 - Turn-key research data management repository
InvenioRDM v5.0 is NOT yet suitable for production services. We are closing in on the release of InvenioRDM 6.0 LTS!
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
We probably need to see if co-body intends to merge/release a fix for this: https://github.com/cojs/co-body/issues/70
Alright, I’ll target it with a PR to handle the removal of the strict shim.