💖 Thanks for opening this pull request! 💖

We use semantic commit messages to streamline the release process. Before your pull request can be merged, you should update your pull request title to start with a semantic prefix.

Examples of commit messages with semantic prefixes:

• fix: don't overwrite prevent_default if default wasn't prevented
• feat: add app.isPackaged() method
• docs: app.isDefaultProtocolClient is now available on Linux

Things that will help get your PR across the finish line:

• Follow the JavaScript, C++, and Python coding style.
• Run npm run lint locally to catch formatting errors earlier.
• Document any user-facing changes you've made following the documentation styleguide.
• Include tests when adding/changing behavior.
• Include screenshots and animated GIFs whenever possible.

We get a lot of pull requests on this repo, so please be patient and we will get back to you as soon as we can.

I couldn't suggest a better home with the current directory structure, but maybe following options can also be considered

1. a component structure which allows sharing code between shell/browser and shell/services/node

  | components
    | net
      | js
        | net-client-request.ts
      | cpp
        | electron_url_loader.cc
        | electron_url_loader.h
      BUILD.gn
  | shell
     | browser
     | common
     | renderer
     | services
       | node
  | lib
    | browser
      | api
        | net.ts => depends on binding exposed from components/net and net-client-request.ts
    | common
    | renderer
    | utility
      | api
        | net.ts => depends on binding exposed from components/net and net-client-request.ts

2. Keep things simple and allow utility to reuse code from browser, we already do this for message ports.

Alright all of the planned follow items are completed here.

For PR description included and stakeholders cc'd, I'm not sure what groups or individuals should be cc'd. I think this requires API review, which looks like it's pending Semver Label Enforcement, but I'm not able to edit the labels here.

Any reviews or guidance through the process is much appreciated! 🙏

Some unrelated changed get pulled in to electron.d.ts due to the version bump of @electron/typescript-definitions. Perhaps that bump should land separately for a bit cleaner separation.

Some unrelated changed get pulled in to electron.d.ts due to the version bump of @electron/typescript-definitions. Perhaps that bump should land separately for a bit cleaner separation.

Sure thing @dsanders11, opened #40264
Thanks for adding the semver label here!

Some unrelated changed get pulled in to electron.d.ts due to the version bump of @electron/typescript-definitions. Perhaps that bump should land separately for a bit cleaner separation.

Sure thing @dsanders11, opened #40264 Thanks for adding the semver label here!

Oh it might be better left as part of this PR actually. Otherwise there are no utility process modules documented and the typescript definition generation fails.

Oh it might be better left as part of this PR actually. Otherwise there are no utility process modules documented and the typescript definition generation fails.

Can @electron/typescript-definitions be fixed so that it doesn't fail in that case? Otherwise we'll be blocked if we need to land a new version of that package before this PR lands, and it may take a bit of time given the large nature of this PR.

Can @electron/typescript-definitions be fixed so that it doesn't fail in that case? Otherwise we'll be blocked if we need to land a new version of that package before this PR lands, and it may take a bit of time given the large nature of this PR.

👍 On it!

Can @electron/typescript-definitions be fixed so that it doesn't fail in that case? Otherwise we'll be blocked if we need to land a new version of that package before this PR lands, and it may take a bit of time given the large nature of this PR.

@dsanders11 opened electron/typescript-definitions#247!

@devm33 looks like the newly added test is failing on linux: https://app.circleci.com/pipelines/github/electron/electron/76406/workflows/f315658a-de1f-4549-93c1-52080f4d7300/jobs/1637154

Release Notes Persisted

Added net module to utility process.

I have automatically backported this PR to "29-x-y", please check out #40890

/trop run backport-to 28-x-y

The backport process for this PR has been manually initiated - sending your PR to 28-x-y!

I have automatically backported this PR to "28-x-y", please check out #40967

@miniak has manually backported this PR to "27-x-y", please check out #40968