refactor: default framework to nextjs on conf init

[matthewvolk]

What/Why?

We use a library called Conf in the Catalyst CLI to persist per-project config data for the CLI. Currently, when you initialize a new .bigcommerce/project.json file (which is done whenever you call a command that interacts with Conf), it sets the "framework" field in .bigcommerce/.project.json to "catalyst" by default. "framework" should only ever be set to "catalyst" after a user has successfully linked their local Catalyst repository to an Ignition project via link, or by providing a --framework override argument.

Testing

Run any command that depends on .bigcommerce/project.json while the file does not yet exist on your machine; the framework field will be set to nextjs (with the exception of the link command)

Migration

N/A

[changeset-bot]

⚠️ No Changeset found

Latest commit: 71fbe9a

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

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
catalyst-b2b	✅ Ready	Preview	Comment	Aug 15, 2025 4:44am
catalyst-canary	✅ Ready	Preview	Comment	Aug 15, 2025 4:44am

3 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
catalyst	⬜️ Ignored			Aug 15, 2025 4:44am
catalyst-au	⬜️ Ignored			Aug 15, 2025 4:44am
catalyst-uk	⬜️ Ignored			Aug 15, 2025 4:44am