Remove no-fund option from .npmrc

[siddharthkp]

What are you trying to accomplish?

Was debugging a breaking workflow and saw a bunch of warnings posing as errors creating noise in the logs

npm warn Unknown env config "no-fund". This will stop working in the next major version of npm.
npm warn Unknown project config "no-audit". This will stop working in the next major version of npm.
npm warn publish "repository" was changed from a string to an object

What approach did you choose and why?

Clean up warnings by removing no-fund and no-audit from .npmrc and fixing repository field in package.json

After:

Can these changes ship as is?

• Yes, this PR does not depend on additional changes. 🚢

[changeset-bot]

⚠️ No Changeset found

Latest commit: f02f13c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[Copilot]

Pull request overview

Removes a deprecated npm environment config entry (no-fund) from the repository’s .npmrc to avoid future npm warnings/breakage.

Changes:

• Removed no-fund=true from .npmrc.

Show a summary per file

File	Description
.npmrc	Drops deprecated no-fund config to prevent “Unknown env config” warnings in newer npm versions.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 1/1 changed files
• Comments generated: 0