fix: port issue with local mockhttp

[jaredwray]

Please check if the PR fulfills these requirements

• Followed the Contributing guidelines and Code of Conduct
• Tests for the changes have been added (for bug fixes/features) with 100% code coverage.

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
fix: port issue with local mockhttp

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a port conflict issue when running local mockhttp tests. By changing the exposed port for the mockhttp Docker container and updating all relevant test configurations to use this new port, it ensures that local development and CI tests can run without port clashes, improving the reliability of the testing environment.

Highlights

• Port Configuration: The mockhttp service in docker-compose.yml was updated to expose port 3737 instead of 3000 to avoid potential conflicts.
• Test Environment: The TEST_URL environment variable used in test scripts and directly in test files (fetch.test.ts, index.test.ts) was updated to http://localhost:3737 to align with the new Docker port mapping.

Changelog

• docker-compose.yml
  • Changed the exposed port for the mockhttp service from 3000:3000 to 3737:3000.
• packages/net/package.json
  • Updated the TEST_URL in test and test:ci scripts from http://localhost:3000 to http://localhost:3737.
• packages/net/test/fetch.test.ts
  • Modified the default testUrl from https://mockhttp.org to http://localhost:3737 when TEST_URL environment variable is not set.
• packages/net/test/index.test.ts
  • Modified the default testUrl from https://mockhttp.org to http://localhost:3737 when TEST_URL environment variable is not set.

Activity

• No specific activity has been recorded for this pull request yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request correctly updates the port for the local mockhttp service to 3737 across the docker-compose.yml, package.json scripts, and test files. The changes are consistent and address the port conflict issue. However, I've noticed that the new test URL is now duplicated in several places. I've added a couple of suggestions to centralize this configuration, which will improve maintainability and make future updates easier.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (a4061ab) to head (26a844a).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #1595   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           26        26           
  Lines         2473      2473           
  Branches       559       559           
=========================================
  Hits          2473      2473           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.