nft VS wrangler-legacy

During next build, Next.js will use @vercel/nft to statically analyze import, require, and fs usage to determine all files that a page might load.

This is because nextjs uses @vercel/nft to determine exactly which files (including node_modules) are necessary for the application runtime.

Currently they use https://github.com/vercel/nft but in the past they use ncc, next.js is using ncc too for compile dependency https://github.com/vercel/next.js/tree/canary/packages/next/compiled, umi (ant.design) internal using ncc to bundling they's deps https://github.com/umijs/umi/blob/master/packages/deps/taskfile-ncc.js

These improvements will be achieved by better dependency tracking using Node File Trace from Vercel (@vercel/nft). This will ensure that only the necessary dependencies are included in the final bundle.

Recently, as a weekend hobby project, I created a Slack app development framework for Cloudflare Workers and Vercel Edge Functions.

Edge Runtime has become a buzzword in the technology landscape, driving dynamic, low-latency functions in platforms from AWS Lambda@Edge and Cloudflare Workers to Vercel Edge. Emphasizing its importance, Vercel recently changed "experimental-edge" to "edge", signaling official support in their popular Next.js framework.

It seems like the perfect usecase for Cloudflare Workers.

For this tutorial, I’ll use Cloudflare Workers as they’re really fast and easy to set up, but you can use pretty much any other serverless provider with support for JS.

Cloudflare has a wonderful serverless platform called Cloudflare Workers that allows you to write code without worrying about underlying hardware or software. Yesterday, they announced that Workers now have the ability to connect directly over TCP sockets. I want to use this feature to send an APRS packet to CWOP.

Sounds doable with Cloudflare Workers