Summary
When
eact-native.packager.port changes after extension activation, existing Packager instances can still hold the previous cached port.
This issue tracks a scoped runtime handling path for that setting without restoring the old noisy configuration-change popup.
Proposed Changes
- Listen only for
eact-native.packager.port configuration changes.
- Refresh cached packager ports when packagers are stopped.
- When a packager is already active, keep the running port unchanged and mark the status bar with a warning indicator.
- Show the pending port in the status bar tooltip using this wording:
- Running on port 8081.
- Port setting changed to 9090. It will be reset on next start.
Test Plan
- Run
pm run build.
- Manually start the packager, change
eact-native.packager.port, and verify the status bar warning and tooltip.
Summary
When
eact-native.packager.port changes after extension activation, existing Packager instances can still hold the previous cached port.
This issue tracks a scoped runtime handling path for that setting without restoring the old noisy configuration-change popup.
Proposed Changes
eact-native.packager.port configuration changes.
Test Plan
pm run build.
eact-native.packager.port, and verify the status bar warning and tooltip.