Marshall Han
Marshall Han
Anyone else who faced `node:async_hook` module resolution problem? I'm using next.js 13 (app router & server action enabled) with @cloudflare/next-on-pages. In the build result `.vercel/output/_worker.js`, I can see: ```js //...
> It is not possible to polyfill all Node APIs or behaviors, but it is possible to polyfill some of them. > > This is currently powered by @esbuild-plugins/node-globals-polyfill which...
oops, I missed that. Thank you @james-elicx ! I could find in English dashboard. added: it just work! succeeded to deploy in production and I can see server action work....
we need to upgrade jsx transformer perhaps
perhaps, [github incident](https://www.githubstatus.com/incidents/ws2l6203cs7g) maybe related? same issue is being happened but hard to reproduce in actual API call as tkaya-ipsi said.
making an express integration example
I believe https://github.com/ueberdosis/tiptap/issues/6332 should be handled before stablizing
could I know what's blocking this?
I'll look this next weekend if no one takes
poisoning DNS with conflict doesn't work to reproduce abvoe. it results: > JSR specifiers are not yet supported in package.json: @std/dotenv@^0.225.5 > JSR specifiers are not yet supported in package.json:...