Releases: curveball/core
Releases · curveball/core
v1.0.2
v1.0.1
v1.0.0
- Finally! Curveball v1. Only took 6 years.
- CommonJS support has been dropped. The previous version of this library
supported both CommonJS and ESM. The effort of this no longer feels worth it.
ESM is the future, so we're dropping CommonJS. - Now requires Node 18.
v0.21.1
v0.21.0
v0.20.0
The Application class now has a fetch() function. This function lets you do an internal HTTP request with the standard Javascript Request and Response objects.
Most of @curveball/core logic has moved to @curveball/kernel, with the exception of any Node.js specific-code. This enables Curveball compatibility with Bun
v0.19.0
- Now requires Node 14.
Application,Context,RequestandResponsenow have aoriginproperty. This defaults defaults tohttp://localhost. This can be overridden by settingApplication.origin, or setting aCURVEBALL_ORIGINenvironment variable.PUBLIC_URIalso works, but it's mainly a fallback for earlier examples and recommendations.RequestandContextnow have aabsoluteUrlproperty. This is calculated based on the request path and theorigin.- BC Break: Due to the new
originproperty, allRequestandResponseclasses now have an extra constructor argument. This means if you ever manually constructed any of these, there's a small change you'll need to make. Typescript should point all these problems! - If
CURVEBALL_TRUSTPROXYis set,request.ip()will trust proxies by default, and return the ip of the real client instead of the proxy.
v0.18.0
This release is identical to the previous alpha version.
Changed in 0.18
- The
Contextinterface has been removed, and theBaseContextclass is renamed toContext. This is a BC break, but should only be an issue if you used theContextinterface directly.BaseContextis still exported but simply aliased toContext. This alias will be removed from a future version. This change should make it easier to use interface declaration merging to extendContext. - The
wsdependency has been updated to version 8. There are some breaking changes in this release. The most likely you'll hit is that incoming messages are now of typeBufferinstead ofstring. Check out the ws changelog for more details.