feat: support custom chromium path and version bump#16
Merged
Conversation
- Add --chromium-path option to CLI for custom browser path - Set PLAYWRIGHT_CHROMIUM_EXECUTABLE_PATH environment variable from CLI option - Update renderer to use process.env.PLAYWRIGHT_CHROMIUM_EXECUTABLE_PATH - Bump all package versions to 0.1.1 Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
jsongo
force-pushed
the
feat/support-chromium-path-v0.1.1
branch
from
83fca98 to
04b1cb5
Compare
jsongo
added a commit
that referenced
this pull request
Feb 7, 2026
- Add --chromium-path option to CLI for custom browser path - Set PLAYWRIGHT_CHROMIUM_EXECUTABLE_PATH environment variable from CLI option - Update renderer to use process.env.PLAYWRIGHT_CHROMIUM_EXECUTABLE_PATH - Bump all package versions to 0.1.1 Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>
jsongo
added a commit
that referenced
this pull request
Feb 7, 2026
* feat: add --chromium-path option and bump version to 0.1.1 (#16) - Add --chromium-path option to CLI for custom browser path - Set PLAYWRIGHT_CHROMIUM_EXECUTABLE_PATH environment variable from CLI option - Update renderer to use process.env.PLAYWRIGHT_CHROMIUM_EXECUTABLE_PATH - Bump all package versions to 0.1.1 Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>
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.
Summary
This PR adds support for specifying a custom Chromium executable path via a new
--chromium-pathCLI option. This is useful for environments where Chromium is located at a non-standard path (e.g., CI/CD, specialized servers).Key changes:
--chromium-pathoption toopen-motion render.@open-motion/rendererto prioritizeprocess.env.PLAYWRIGHT_CHROMIUM_EXECUTABLE_PATH.0.1.1.Test plan
--chromium-path.--chromium-pathand verify it fails with a clear message.0.1.1.🤖 Generated with Claude Code