fix: skip dynamic bazaar import when extension is pre-registered #982
+22
−8
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.
Background
The
@x402/next(and other HTTP middleware) packages use dynamic imports with/* webpackIgnore: true */for the bazaar extension:This fails on serverless platforms (e.g., Vercel) because:
webpackIgnoretells the bundler to resolve the module at runtimenode_modulesERR_MODULE_NOT_FOUNDFrom Vercel:
Solution
Update all HTTP middleware packages (next, express, hono) to skip the dynamic import when the extension is pre-registered
Users on serverless platforms can now pre-register the bazaar extension using a static import:
hasExtension("bazaar")returnstrueUsers on traditional servers (where
node_modulesis available) see no change in behavior.