Remove http-proxy-node16, replace with lightweight inline proxy

[ryancbahan]

Summary

• Add http-proxy.ts (~100 lines) implementing web() and ws() proxy methods using Node's built-in http/https modules
• HTTP forwarding: pipes request to target, pipes response back with headers
• WebSocket forwarding: handles upgrade handshake, bidirectional socket piping, proper error cleanup
• Remove http-proxy-node16 from packages/app/package.json

Tophatting

• confirm shopify app dev still works as expected
• confirm dev console in admin still receives ws updates from cli

[ryancbahan]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• Remove is-interactive, inline the TTY check #7198
• Remove http-proxy-node16, replace with lightweight inline proxy #7196 👈 (View in Graphite)
• Remove network-interfaces, use os.networkInterfaces() directly #7195
• Remove camelcase-keys, replace with inline utility #7194
• Remove ansi-colors, replace with lightweight inline utility #7193
• Remove tmp and @types/tmp dependencies #7192
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

We detected some changes at packages/*/src and there are no updates in the .changeset.
If the changes are user-facing, run pnpm changeset add to track your changes and include them in the next release CHANGELOG.

Caution

DO NOT create changesets for features which you do not wish to be included in the public changelog of the next CLI release.

[gonzaloriestra]

I'm not sure about this change. I agree with replacing simple libraries with our own code, but this looks a bit complex (even if it's small)...

For example, some concerns by Claude that were apparently handled by the library:

1. connection: 'close' on every proxied request — this disables keep-alive, which could add latency for repeated requests to the same backend during app dev. A battle-tested proxy library would handle connection pooling properly.
2. Manual HTTP response construction in WS upgrade — writing raw HTTP/1.1 101 Switching Protocols\r\n... strings is fragile. Edge cases around header formatting (multi-value headers, encoding) can cause subtle breakage.
3. No timeout handling — if a backend hangs, the proxy request will hang indefinitely.

[ryancbahan]

@gonzaloriestra I hear you, but I think a simple proxy/reverse proxy is something node can do well and that we can manage. But I definitely want to ask for broader team perspective here. @byrichardpowell @dmerand @isaacroldan what do y'all think? If there's alignment that this is a good dep removal candidate, I'll harden the tests and ensure those cases you pointed out are derisked. Else, I'll close.

[byrichardpowell]

Yeah, this one is not a clear candidate for removal imo. It seems like http-proxy-node16 hasn't had many updates in the last 24 months, so it's not really a maintenance sink. I also echo Gonzalo's concern about edge cases. Although I haven't looked into the practical implications of Gonzalo's points my instinct is to leave this one alone.