Conversation
Member
Author
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
How to use the Graphite Merge QueueAdd either label to this PR to merge it via 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 required 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. |
graphite-app
bot
changed the base branch from
01-15-docs_update_polyfills_docs
to
graphite-base/5928
longlho
force-pushed
the
01-15-build_rm_pinned_dep
branch
from
1e58dae to
750738b
Compare
longlho
force-pushed
the
graphite-base/5928
branch
from
292421c to
3275da3
Compare
Merge activity
|
longlho
force-pushed
the
01-15-build_rm_pinned_dep
branch
from
750738b to
be567c4
Compare
This was referenced Jan 15, 2026
graphite-app bot
pushed a commit
that referenced
this pull request
Jan 15, 2026
### TL;DR Remove `@brillout/vite-plugin-server-entry` from package resolutions. ### What changed? Removed the `@brillout/vite-plugin-server-entry: '>=0.7.17'` entry from the resolutions field in both `package.json` and `pnpm-lock.yaml`. This change also resulted in updates to various digest values in the `MODULE.bazel.lock` file. ### How to test? 1. Run `pnpm install` to verify the package installation works without issues 2. Run the test suite to ensure all functionality continues to work as expected 3. Verify that any components using Vite continue to build and function correctly ### Why make this change? The resolution override for `@brillout/vite-plugin-server-entry` is likely no longer needed, possibly because: 1. The minimum version requirement is now met by default in the dependency tree 2. The package is no longer used in the project 3. Any issues that required pinning this dependency have been resolved Removing unnecessary resolution overrides helps keep the dependency management cleaner and reduces potential conflicts.
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
1 participant
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.
TL;DR
Remove
@brillout/vite-plugin-server-entryfrom package resolutions.What changed?
Removed the
@brillout/vite-plugin-server-entry: '>=0.7.17'entry from the resolutions field in bothpackage.jsonandpnpm-lock.yaml. This change also resulted in updates to various digest values in theMODULE.bazel.lockfile.How to test?
pnpm installto verify the package installation works without issuesWhy make this change?
The resolution override for
@brillout/vite-plugin-server-entryis likely no longer needed, possibly because:Removing unnecessary resolution overrides helps keep the dependency management cleaner and reduces potential conflicts.