nodecaf - npm Package Versions

[v0.12.6] - 2023-09-11

Added

• app.run() to start and setup, handle process signals and log crashes

[v0.11.14] - 2023-09-11

Added

• app.run() to start and setup, handle process signals and log crashes via cli

[v0.13.3] - 2023-08-22

Deprecated

• signed option of res.cookie()

Added

• capability for reading chunked body as if it was a complete body to body.raw()

Fixed

• error when logging warn about res.end() being called more than once
• app.stop() to preserve globals so callbacks trying to access them don't fail
• path param processing to accept and decode uri escape characters

[v0.13.2] - 2022-06-08

Added

• app.run() to start and setup, handle process signals and log crashes
• missing del route builder to main export

Removed

• wrong field from request body type definition
• accidental non-standard http methods from main export

Deprecated

• Nodecaf.run() in favor of app.run()

Changed

• body handler to inherit the native IncomingMessage stream behavior
• res handler to inherit the native ServerResponse stream behavior
• app.setup() to accept multiple spread conf objects/paths

[v0.13.1] - 2022-06-07

Added

• run from separate package to ensure version compatibility
• missing all route builder to main export

Fixed

• body parsing to not attempt parsing when no body is sent

Deprecated

• api constructor option in favor of routes

[v0.13.0] - 2022-03-29

Added

• keep() handler method to store a variable in handler args for the lifetime of the request
• client ip address to handler args
• warning when res.end() is called more than once
• websocket() handler method to work with ws upgrades
• opts.routes as an experimental alternative way to define routes

Changed

• body.req to body.stream
• app.trigger() to be completely isomorphic with calls coming from http requests
• body parsing to timeout after 4 seconds if no bytes were received

Removed

• fork(), flash, next() & middleware-style chaining in favor of single handler and call()
• pre() and pos() in favor of using call()
• opts.alwaysRebuildAPI in favor of using opts.conf and variadic routes
• req from handler args in favor of method and path

Fixed

• request without a content-type header defaulting to parse body as text
• body parsing to properly handle errors both on manual and automatic