Registry fetch failing / website down? (ECONNRESET when adding components)

[arhamscripts]

Hi, I’m setting up react-native-reusables in an Expo SDK 54 + pnpm + NativeWind project on Windows.

Project init/diagnostics worked, but adding components fails because the registry URLs on the website seem unreachable.

pnpm dlx @react-native-reusables/cli@latest init

Then when trying to add components, I get:

request to https://reactnativereusables.com/r/nativewind/button.json failed, reason: read ECONNRESET

It also fails on other component registry URLs like:

• card.json
• input.json
• text.json
• label.json

Question

Is the registry / website currently down, or is there another recommended way to add components right now?

If there’s a manual fallback or alternate registry source, I’d love to know.

Thanks!

[mrzachnugent]

Hey @dev-arham ,

The registry is not down. If the URLs are opening in your browser, then everything is up and serving correctly. This is almost always a network/TLS issue on the client side, not a problem with the registry itself.

ECONNRESET means the connection is being forcefully closed during the request. We’ve seen this happen in a few environments, especially with:

• Windows + pnpm
• VPNs / corporate networks
• aggressive antivirus / firewall software
• Node/Bun TLS quirks

Things to try

A few things that have fixed this for others:

1. Try without pnpm (just to isolate)

npx @react-native-reusables/cli@latest add button

2. Disable VPN / proxy / antivirus temporarily

These commonly interfere with Node HTTPS requests even when the browser works fine.

3. Try a different network

Hotspot is a quick way to confirm if it’s network-related.

4. Update Node

Make sure you're on a recent LTS.

5. Retry (it can be transient)

Sometimes this error is just a flaky connection.

Why this happens

Browsers are much more resilient with retries, TLS fallbacks, and proxy handling. The CLI uses Node’s HTTP stack, which is stricter and more sensitive to interruptions so you can see failures there even when the URL works fine in a browser.

Manual fallback

If you're blocked, every component on reactnativereusables.com has a Manual tab in the instructions section.

You can use that instead of the CLI:

1. Open the component page on the website
2. Go to the Instructions section
3. Select the Manual tab
4. Follow the listed setup steps for that component

[arhamscripts]

Hi @mrzachnugent ,

Thanks for the detailed troubleshooting steps!

It turns out the issue was on my side. My VPN was interfering with the CLI requests. Once I connected through a different network setup, the registry commands worked perfectly.

Really appreciate the guidance and the manual fallback instructions as well. Everything is working smoothly now!

Thanks again for your help ^-^