Make sure to use the public npm registry instead of the private shopify one

[jas7457]

Background

When trying to install a new module / update an existing one, sometimes this repo was resolving to the private shopify npm registry, which this repo does not have access to. This happens for people who have a user npmrc ~/.npmrc

Solution

This explicitly sets the npm registry, overriding any user-defined ones.

🎩

• Make sure you have the private registry set
• Delete the entry in yarn.lock for this module
• Run yarn
• Ensure that it resolves to the public registry now, whereas in main, it will not.

Checklist

• I have 🎩'd these changes
• I have updated relevant documentation

Note

Even though I am telling it to use npmjs.org, it is resolving to yarnpkg.com. I asked claude about this, because that was unexpected. It is no longer resolving to the private repo (like it was before), but this was still unexpected. It made it sound like that's expected in yarn v1.

[github-actions]

We detected some changes in packages/*/package.json or packages/*/src, and there are no updates in the .changeset directory. If the changes are user-facing and should cause a version bump, run yarn changeset to track your changes and include them in the next release CHANGELOG. If you are making simple updates to repo configuration, examples, or documentation, you do not need to add a changeset.