fix: rename PORT to WATT_ADMIN_PORT to avoid .env collisions#175
Merged
fix: rename PORT to WATT_ADMIN_PORT to avoid .env collisions#175
Conversation
PORT is a very common env var used by many tools and projects. Using it as the server port placeholder in watt.json meant any .env file with PORT set would unintentionally change the admin dashboard port. Co-Authored-By: Claude Opus 4.6 <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
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
PORTenv var toWATT_ADMIN_PORTacross the project (watt.json,lib/start.js,.env.sample, tests, Playwright config)PORTis a very common env var used by many tools and projects; having it as the Watt config placeholder meant any.envfile withPORTset would unintentionally override the admin dashboard portTest plan
npm run test:cli— 7/7).envwithPORT=3000no longer affects the dashboard port🤖 Generated with Claude Code