As I write those lines, I'm on a short flight between Bologna and Amsterdam for the week. Soon, I'll be keynoting JSNation with my Co-Founder and CEO Luca Maraschi, announcing the whole scale of Platformatic goals to the world. While we have been shipping weekly releases and constant improvement, we seldom presented the tech world with our goal. We are unveiling the new things we worked on in the last few months. On June 1st, we are releasing something new that was not possible before with Node.js.
Register at https://papilio.platformatic.dev/launch-signup to for all details.
A community member (Mateo Nunez) reported a bug on the Platformatic Discord channel, and he created an excellent reproduction: https://github.com/mateonunez/plt-programmatic-rules-error-reproduction. In this video, we worked together to fix that bug, and we made two pull requests:
In the next stream, we work on three different problems.
encapsulate: falseoption for loading plugins, it also refactors the loading of the application configuration as well as several bugfixes; v0.25.0 fixes a few regressions introduced in v0.24.0, as well as improving the GitHub actions generator for Platformatic Cloud.
destroy()method; v0.3.0 adds all the missing
Dispatchermethods; v0.3.1 drops the connection and transfer-encoding headers, if specified; v0.4.0 adds a
domainoption to support fast-fail scenarios.
destroyAgentoption to skip destroying the agents when the Fastify instances closes.
cacheControlto control caching in CDN.
content-typecannot be determined by file extension.
A critical mention goes to
@types/node to have finally replaced the
@deprecated tag with a new
@legacy one in PR #65506. Legacy functions are not deprecated; we do not plan to remove them, but we do not recommend to be used for new implementations.