fix: inline axios so cloudflare_module Worker deploy succeeds#126
Merged
Conversation
posthog-node lazily requires axios; with the cloudflare_module preset Nitro leaves it as an external require that wrangler's esbuild cannot resolve in .output, failing the deploy. Inlining axios via Nitro externals reproduces the prior bundling behaviour. https://claude.ai/code/session_012YWscdohmouZHhZ7otKnqh
This was referenced May 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Follow-up to #125. The
cloudflare_modulepreset is now onmain, but the Worker deploy fails:posthog-node(used server-side bynuxt-posthog) does a lazyrequire("axios"). Under the oldcloudflare_pagespreset Nitro bundled everything itself; undercloudflare_moduleNitro leavesaxiosas an externalrequirethat wrangler's esbuild cannot resolve in.output(nonode_modulesthere).Change
axiostonitro.externals.inlineso Nitro bundles it into the server output, reproducing the prior bundling behaviour. Runtime behaviour is unchanged (the same code already ran in the previous Pages Worker).One-line change in
nuxt.config.ts.Test plan
wrangler deploycompletes without theCould not resolve "axios"errorhttps://claude.ai/code/session_012YWscdohmouZHhZ7otKnqh
Generated by Claude Code