Skip to content

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Dec 9, 2025

No description provided.

@joyeecheung joyeecheung marked this pull request as ready for review December 9, 2025 14:07
@joyeecheung joyeecheung requested a review from a team as a code owner December 9, 2025 14:07
@kyliewd
Copy link

kyliewd commented Dec 9, 2025

@joyeecheung -- heres some alternate copy that might work a little better for socials!

version 1
Working in an enterprise setup with corporate proxies or custom CAs? Node.js has native support for that.

No extra steps required, just configure and continue 👍

Details: https://nodejs.org/en/learn/http/enterprise-network-configuration

version 2
If Node.js keeps failing inside your company network, we've released a new guide that covers proxy settings and system CA setup.

Nothing flashy, just the basics you need to get things done. 💪

Guide here: https://nodejs.org/en/learn/http/enterprise-network-configuration

@joyeecheung
Copy link
Member

joyeecheung commented Dec 9, 2025

Thanks for the suggestions, I like the version 1 although I think

No extra steps required, just configure and continue 👍

might be over simplifying it a bit - in many corporate environments, you likely do need to do some internal setups that would've been otherwise easy in non-corporate ones (e.g. Node.js is run in another company tool, and you may or may not have control over the command line arguments). Though I think this might be accurate:

No external dependency required, just configure and continue 👍

The primary good news is really that Node.js now has built-in support for this and you no longer need to use a third-party dependency that doesn't work across all platforms or uses some undocumented Node.js APIs that can break at any time, also companies might feel more comfortable with using built-ins for something as sensitive as system CA support than relying on an npm package. So I'd suggest:

Working in an enterprise setup with corporate proxies or custom CAs? Node.js has native support for that.
No external dependency required, just configure and continue 👍
Details: https://nodejs.org/en/learn/http/enterprise-network-configuration

@joyeecheung
Copy link
Member

Thanks @kyliewd - BTW you can more explicitly approve it (i.e. leave a trace on GitHub) if you go to "Files changed" tab, click "Review changes" green button on the right and select "Approve" and then submit.

Do you want to post this manually on bluesky? In this repo if we click the "squash and merge" button above the comment box it will trigger the automation to just post the proposed text to the official account of bluesky, I think you should already have the permissions to click the button so feel free to just use the automation instead of logging in manually; we'd still need you to post the text proposed here to other channels manually though.

@kyliewd
Copy link

kyliewd commented Dec 10, 2025

thanks joyee! will get this published.

@kyliewd kyliewd merged commit ce45c80 into main Dec 10, 2025
1 check passed
@kyliewd kyliewd deleted the action/a0c0a963-496e-4c3f-8821-32f63721c091 branch December 10, 2025 15:31
github-actions bot added a commit that referenced this pull request Dec 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants