fix(js-utils): correctly handle esbuild with import-statement not matching node stdlib #2067
Conversation
This file contains 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
This was referenced Feb 22, 2025
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
PR Summary
This pull request focuses on fixing ESBuild import handling in the JavaScript utilities, specifically addressing Node.js standard library import statement mismatches.
- Added
.github/workflows/autofix.ci.ymlto automatically fix code formatting using Biome in frontend, site, and SDK directories - Added
.github/workflows/fe-pull-request.ymlto run code quality checks on frontend-related changes - Added
.github/workflows/rust.yamlto handle Rust-specific CI checks including formatting and dependency validation - Added
.github/workflows/release.yamlto manage versioned releases with binary builds and Docker image creation - Added
.github/workflows/pkg-pr-new.yamlto automate package publishing for approved pull requests
No file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile
This was referenced Feb 22, 2025
How to use the Graphite Merge QueueAdd the label merge-queue to this PR to add it to the merge queue. You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
Deploying rivet with
|
| Latest commit: |
1428171
|
| Status: | ⚡️ Build in progress... |
MasterPtato
force-pushed
the
02-21-fix_fdb_conflict_ranges
branch
from
652c945 to
d498e79
Compare
NathanFlurry
changed the base branch from
02-21-fix_fdb_conflict_ranges
to
graphite-base/2067
NathanFlurry
force-pushed
the
graphite-base/2067
branch
from
d498e79 to
652c945
Compare
NathanFlurry
changed the base branch from
graphite-base/2067
to
02-21-fix_fdb_conflict_ranges
This was referenced Feb 22, 2025
…ching node stdlib
NathanFlurry
changed the base branch from
02-21-fix_fdb_conflict_ranges
to
graphite-base/2067
NathanFlurry
force-pushed
the
graphite-base/2067
branch
from
652c945 to
6ccf25c
Compare
NathanFlurry
force-pushed
the
02-21-fix_js-utils_correctly_handle_esbuild_with_import-statement_not_matching_node_stdlib
branch
from
52a882d to
1428171
Compare
Merge activity
|
graphite-app bot
pushed a commit
that referenced
this pull request
Feb 22, 2025
…ching node stdlib (#2067) <!-- Please make sure there is an issue that this PR is correlated to. --> ## Changes <!-- If there are frontend changes, please include screenshots. -->
graphite-app
bot
deleted the
02-21-fix_js-utils_correctly_handle_esbuild_with_import-statement_not_matching_node_stdlib
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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