-
Notifications
You must be signed in to change notification settings - Fork 1
legacy-issue-fix #596
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
nandap4790
wants to merge
2
commits into
master
Choose a base branch
from
legacy-issue-fix
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+22,475
−23,511
Open
legacy-issue-fix #596
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Verification agent
🧩 Analysis chain
Port switch to 8081 looks right—please verify no stale 8080 references remain and that cross-device dev works.
This aligns with the new webpack devServer port. To avoid surprises:
Run:
🏁 Script executed:
Length of output: 873
Synchronize asset server port references to 8081
We’ve confirmed the
asset_hostinconfig/publisher.ymlis correctly set tohttp://localhost:8081, but there are still stale uses of port 8080 elsewhere. Please update the following so your local and cross-device workflows continue to work:Currently mapping
["8080:8080"]. Change this to["8081:8081"](or your chosen host:container ports) so the asset server matching webpack’sdevServer.portis exposed.Update the SSH tunnel from
-L 8080:localhost:8080to-L 8081:localhost:8081(and any other forwarded ports) to mirror the new asset-server port.It runs
sed -i "" 's/asset_host:.*$/asset_host:/' config/publisher.yml. Ensure any automation around resetting or templating theasset_hoststill works as intended now that the URL includes:8081.Revise instructions around
config/publisher.yml(e.g. “remove the asset_host”) to reflect that the default dev port is now 8081, and note any manual edits needed.Remember that
localhostwon’t resolve on other devices. We recommend enabling an env-driven host (e.g.ASSET_HOST=http://192.168.x.y:8081) or documenting the LAN IP in your README for phone/tablet testing.Once these updates are in place, rerun the grep checks to confirm no
:8080references remain and verify you can access the asset server both locally and from another machine.🤖 Prompt for AI Agents