pallid rampart
I maintain an npm package that needs to make HTTP requests. Previously I've been using a dynamic import to node-fetch if globalThis.fetch is not present.
With Vite 4.3 users see the warning introduced in https://github.com/vitejs/vite/commit/72050f9 when they use this library. Is there a recommended strategy to provide fetch to Node.js 16 and 17 which don't have it, while not bundling this dependency for the browser?
pallid rampart
In their Next.js package Clerk
uses subpath imports - is this something I can rely on most bunders to understand?
https://nodejs.org/api/packages.html#subpath-imports
https://github.com/clerkinc/javascript/blob/58a3db6e8371a570da5ed9e306535c379d0e314d/packages/backend/package.json#L17
pallid rampart
I'm considering https://www.builder.io/blog/stop-polyfilling-fetch-in-your-npm-package but this would be a significant change.
pallid rampart
Thinking about making a dedicated Node.js build now that uses node-fetch.