Dynamic import of `proxy-agent` breaks bun single executable bundling

[vladfrangu]

Source code:

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({
	token: process.env.APIFY_TOKEN,
});

const me = await client.user('me').get();

console.log(me);

Running like this works: APIFY_TOKEN="apify_api_you_wish" bun src/index.ts

Building into a single executable like so: bun build src/index.ts --target node --compile --outfile apifyclient followed by running it does not, and throws error: Cannot find package 'proxy-agent' from '/$bunfs/root/apifyclient'

In apify-cli I had to basically build bundles in 2 steps:

1. single file executable that manually imports proxy-agent by adding in a import {} from "proxy-agent"
2. patch the result to reference the manual import.

See the diff from the PR

[barjin]

I believe this is essentially the same as #852 . The current setup doesn't expect the use of bundlers with Node environments.

Perhaps we can update the bundling setup (the one here, generating ./bundle.js), so it drops the isNode() blocks altogether, but keeps the imports discoverable when importing apify-client (not apify-client/browser).

[klclee]

+1 for this issue. it compeletly breaks turbo build for next 16.2.1 and there is no way round it.

just to add context. I have to argue with teh secuity guys why i can t upgrade then if I do i am getting nailed by the guiys paying for apify saying why are we not using it.. pls fix.