Fix memory leak by removing custom net/tls polyfills

[astralhpi]

Problem

Custom Socket polyfill implementation was causing memory leaks in Cloudflare Workers environments.

Solution

Removed custom net/tls polyfills since Cloudflare Workers now provide built-in polyfills for these modules.

Changes

• Removed custom net/tls polyfill imports from Cloudflare build
• Updated transpilation to use Cloudflare's built-in polyfills instead

Result

• Fixes memory leak in Worker environments

Reproducer: https://github.com/astralhpi/cf-worker-memory-leak-sample

[porsager]

Fantastic ! Do you have any idea for running the tests for Cloudflare Workers too?

[astralhpi]

Unfortunately, automated memory leak testing in Workers is difficult - profiling requires manual Chrome DevTools inspection via Wrangler dev, and production workers auto-respawn on crash.
My sample project could serve as a starting point for basic functionality tests, but memory leak detection would still need manual verification.

[danieltroger]

Hi, I think I need this. I have logs of multiple CF queue handlers which did nothing except having a postgres.js connection open (just waited for the answer (that never came) of an RPC call for 8.4 minutes, using 10ms CPU time) and then died with OOM (Worker exceeded memory limit.).

It literally makes no sense at all, and this is my only possible explanation/fix that's not completely out there.

Is there any way to preview this/could it be merged?