Repository navigation
fix: use one-arg import.meta.resolve for Bun compatibility - #2607
Merged
Merged
Conversation
Bun's two-arg import.meta.resolve(specifier, parent) fails for bare package names (Cannot find package 'wxt' / '@wxt-dev/…'). One-arg resolve works on both Bun and Node, so WXT CLI can run under bun --bun / bunx --bun.
✅ Deploy Preview for creative-fairy-df92c4 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
github-actions
Bot
added
the
pkg/wxt
Contributor
Author
|
Companion Bun issue for the two-arg |
nishu-murmu
requested review from
PatrykKuniczak and
nishu-murmu
as code owners
October 3, 2026 04:44
nishu-murmu
enabled auto-merge (squash)
October 3, 2026 04:44
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
aklinker1
disabled auto-merge
October 4, 2026 05:55
aklinker1
approved these changes
Oct 4, 2026
Co-authored-by: Aaron <aaronklinker1@gmail.com>
aklinker1
changed the title
import.meta.resolve for Bun compatibility
aklinker1
enabled auto-merge (squash)
October 4, 2026 05:57
@wxt-dev/analytics
@wxt-dev/auto-icons
@wxt-dev/browser
@wxt-dev/i18n
@wxt-dev/is-background
@wxt-dev/module-react
@wxt-dev/module-solid
@wxt-dev/module-svelte
@wxt-dev/module-vue
@wxt-dev/runner
@wxt-dev/storage
@wxt-dev/unocss
@wxt-dev/webextension-polyfill
wxt
commit: |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2607 +/- ##
==========================================
- Coverage 79.63% 79.52% -0.11%
==========================================
Files 138 138
Lines 4114 4113 -1
Branches 943 943
==========================================
- Hits 3276 3271 -5
- Misses 740 743 +3
- Partials 98 99 +1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Contributor
|
Thanks for helping make WXT better! |
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
3 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
import.meta.resolve(specifier, parent)fails for bare package names (Cannot find package 'wxt'when resolving from inside the package, and the same for WXT modules with a synthetic…/index.jsparent).resolveWxtModuleDirandresolveWxtUserModulesto one-argimport.meta.resolve, which works on both Bun and Node.bunx --bun wxt/bun --bunrun the WXT CLI (verified: HMR + production build).Related
import.meta.resolvepackage-name failures.Test plan
bunx --bun wxt --helpin a project that depends onwxtbunx --bun wxt(dev) starts withoutCannot find package 'wxt'@wxt-dev/unocss(or othermodules:) still loads modules under Bun and Nodenpx wxt/node …/wxt.mjsstill works