Conversation
🦋 Changeset detectedLatest commit: 6fa15d6 The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
github-actions
bot
added
the
pkg: astro
CodSpeed Performance ReportMerging #13833 will not alter performanceComparing Summary
|
Member
|
Ouch, it seems that edge middleware tests are failing |
ematipico
approved these changes
May 21, 2025
Merged
openscript
pushed a commit
to openscript/astro
that referenced
this pull request
Sep 12, 2025
* fix: polyfill import.meta.resolve * Don't resolve at runtime * Linit
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.
Changes
Ponyfills
import.meta.resolve, because it's behind a flag in Node.js 20.3-20.5. Theimport-meta-resolvepackage is already a dep of@astrojs/markdown-remark. We can't use it at runtime because of node builtins, so we split it into different functions, where the runtime one doesn't resolve the name and we import it directly. It's only important at build time, as it allows us to bundle the driver.Fixes #13800
Testing
Session tests pass. Tested with Node 20.4
Docs