Difference between bun run and running the compiled binary - Deprecation warning url.parse

[nickhobbs94]

What version of Bun is running?

1.2.0+b0c5a7655

What platform is your computer?

Darwin 23.6.0 arm64 arm

What steps can reproduce the bug?

If I perform any axios request with a script envoked with bun run index.ts I see no deprecation warnings. But if I run the same script with bun build --compile index.ts --outfile out, ./out I see a DeprecationWarning for url.parse().

Here's an example script that shows the behaviour:

import axios from "axios";

const response = await axios.get('https://example.com');

What is the expected behavior?

I'd like to not see any unexpected deprecation warnings after compiling the binary. I'd be happy to simply turn off the warnings for the compiled binary.

What do you see instead?

DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
 code: "DEP0169"

      at urlParse (node:url:32:45)
      at getProxyForUrl (/$bunfs/root/out:9442:56)
      at setProxy (/$bunfs/root/out:11622:66)
      at <anonymous> (/$bunfs/root/out:11867:15)
      at dispatchHttpRequest (/$bunfs/root/out:11685:57)
      at <anonymous> (/$bunfs/root/out:11671:18)
      at new Promise (1:11)
      at wrapAsync (/$bunfs/root/out:11654:10)
      at dispatchRequest (/$bunfs/root/out:12640:17)

Additional information

I'm using axios 1.7.9 if that helps.

No response

[DonIsaac]

Deprecation warnings for url.parse() are not emitted for files within node_modules. Bun determines this by scanning the call stack. You're seeing this warning now since compiled binaries have their paths clobbered.

[DonIsaac]

I'll make this warning respect process.noDeprecation. Once merged, just set it to true and you should be good to go.

[nickhobbs94]

Awesome! Thank you.