Resolving the Could Not Resolve async_hooks Error When Deploying Cloudflare CLI with npx

If you’ve encountered the following error while deploying the Cloudflare CLI using the command:

npx @cloudflare/next-on-pages@1

you’re not alone. This issue occurs due to the fact that the async_hooks package is not found on the file system, as it’s built into Node.js. The error looks something like this:

[ERROR] Could not resolve "async_hooks"
...
The package "async_hooks" wasn't found on the file system but is built into
Node. Are you trying to bundle for node? You can use "platform: 'node'" to do
that, which will remove this error.

Root Cause

This error is caused because async_hooks is a Node.js core module, and the bundler attempts to resolve it from the file system instead of treating it as a Node.js built-in.

Solution

The easiest and recommended solution is to use the latest version of the Cloudflare CLI deployment command. Instead of using:

npx @cloudflare/next-on-pages@1

Use the following updated command:

npx @cloudflare/next-on-pages@latest

This ensures that you are using the most recent version of the tool, which includes fixes for compatibility issues, including the one related to async_hooks.

Why This Works

The latest version of the @cloudflare/next-on-pages package addresses this issue by properly handling Node.js core modules like async_hooks, ensuring that the bundler doesn’t try to resolve them as if they were external dependencies.

Additional Tips

• Keep Your Dependencies Updated: Regularly update your dependencies to avoid such errors.

• Check for Compatibility: When using specific Node.js versions, ensure the tools and libraries you’re using are compatible.

• Review Documentation: Always refer to the official documentation for the latest commands and best practices.

By switching to the latest version of the @cloudflare/next-on-pages package, you can seamlessly deploy your Cloudflare CLI without running into the async_hooks error.