Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(node/url): respect process.noDeprecation in url.parse() #16641

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

DonIsaac
Copy link
Contributor

@DonIsaac DonIsaac commented Jan 23, 2025

What does this PR do?

Closes #16639

How did you verify your code works?

Existing node:url tests cover most of this behavior. I've added tests for the rest.

@robobun
Copy link

robobun commented Jan 23, 2025

Updated 8:00 PM PT - Jan 23rd, 2025

@DonIsaac, your commit a7ea7c7 has some failures in #10421


🧪   try this PR locally:

bunx bun-pr 16641

@DonIsaac DonIsaac requested review from a team and cirospaciari and removed request for a team January 23, 2025 07:02
src/js/node/url.ts Outdated Show resolved Hide resolved
DonIsaac and others added 2 commits January 23, 2025 11:14
Co-authored-by: Jarred Sumner <jarred@jarredsumner.com>
@Jarred-Sumner
Copy link
Collaborator

Can we just not print any of these deprecation warnings and comment out the tests that check they get printed? Or pass some flag to opt in to printing them we pass to node tests? It’s really noisy and offers no value for users most of the time

@DonIsaac
Copy link
Contributor Author

url.parse() warning is gone. I've left the other one b/c it warns about correctness.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

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