Repository navigation
fix: resolve caller data paths in Playwright UI - #122
Merged
Merged
Conversation
longlho
marked this pull request as ready for review
October 9, 2026 16:55
longlho
pushed a commit
that referenced
this pull request
Oct 10, 2026
🤖 I have created a release *beep* *boop* --- ## 3.9.0 (2026-10-09) ## What's Changed * feat: prune source maps from browser input directories by @longlho in #114 * fix: let callers control browser test selection by @longlho in #116 * fix: preserve npm package paths in runtime inputs by @longlho in #117 * fix: allow remote caching for local browser tests by @longlho in #119 * fix: leave host browser execution restrictions to callers by @longlho in #120 * feat: aggregate E2E suites in local Playwright UI by @longlho in #121 * fix: resolve caller data paths in Playwright UI by @longlho in #122 * fix: build Playwright UI bundles as declared Bazel outputs by @longlho in #123 **Full Changelog**: v3.8.1...v3.9.0 --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
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.
Integrating Playwright UI with a real application's preview server requires caller data paths in environment variables. The UI launcher currently hides those direct dependencies behind its manifest target, preventing Bazel from expanding
$(rootpath ...)references.Expose caller
datadirectly to the developer executable and run compiled Playwright from the workspace's runfiles directory, where expanded rootpaths resolve. Source-mode working-directory behavior is unchanged.The nested-suite discovery fixture now reads declared package data through an expanded environment path, covering both prerequisite expansion and runtime path resolution.