Last week was a big week for me and the team at Platformatic– we finally launched v1.0.0, and I could not be more excited to share it all with you!
This launch is important because it includes features I was desperate to have during my many years as a software consultant. What we released last week would have saved me countless hours, headaches, and deployment errors. While I can’t turn back the clock, I look forward to seeing others in my position have access to Platformatic and avoid these issues. So, what did we ship?
Lastly, my co-founder Luca and I answered some of the main questions we received in the days after the launch went live. You can check that out here: https://www.youtube.com/watch?v=oOrQm-95TWQ
Are you still developing commonjs applications, or have you switched to ESM for everything? The team at Node.js has been quite busy, and a new experimental flag appeared:
--experimental-default-type=module. This changes the default module type of
js file extensions from
.mjs becomes the default.
This flag changes a few things about how modules are loaded:
ESM-only packages, like
node-fetch: The flip has no effect on either the package author or its consumers.
CommonJS-only packages, like
fastify; have no effects for its consumers. Maintainers need to add
"type": "commonjs" to
In Node v20.x, we have been seeing many hung processes remaining "hung" and not completely. This concerns Native/V8 Code Coverage integration with Node.js, executing code in
FinalizationRegistry, and possibly a few more cases.
We are discussing this issue in Node.js core at #49344.
I've shipped two "duck tape" fixes in pino and undici to help address this issue, which both disable the
Tap also shipped a hot fix to reduce the frequency of the problem in #934.
Please let me know if you are experiencing this issue as well.
addToBodyand return files as buffers when
attachFieldsToBodyis set to