feat: Export ./package.json in exports field for Module Federation support

[AfeefRazick]

Context

This change addresses an issue raised in Issue #1060: currently, package.json isn’t listed in the "exports" field of the package. Tools like Vite Module Federation rely on this entry to resolve the package correctly.

What’s Changed

• Added "./package.json": "./package.json" to the "exports" field in package.json.

Why It Matters

• Module Federation compatibility: Without this entry, Vite Module Federation fails to locate and load package.json, resulting in resolution errors
• Consistency: Aligns with patterns used by other libraries that explicitly export their package.json when needed.

Steps to Verify

1. Install the updated nuqs package in a Vite-based project with Module Federation enabled.
2. Attempt to import or load the package.
3. Build module federation project to confirm that there are no resolution errors related to package.json.

Closes #1060.

[vercel]

@AfeefRazick is attempting to deploy a commit to the 47ng Team on Vercel.

A member of the Team first needs to authorize it.

[pkg-pr-new]

pnpm add https://pkg.pr.new/nuqs@1062

commit: 5e020fb

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Project	Deployment	Preview	Comments	Updated (UTC)
nuqs	✅ Ready	Preview	Comment	Aug 14, 2025 2:40pm

[github-actions]

🎉 This PR is included in version 2.5.0-beta.5 🎉

The release is available on:

• npm package (@beta dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 2.5.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀