feat(cli): use custom opennext config path in new opennextjs cli release

[matthewvolk]

What/Why?

Cloudflare's OpenNext team recently released @opennextjs/cloudflare 1.8.0 which includes a feature request we discussed here. This PR makes use of that new flag... thanks Cloudflare!

Testing

✅ CI Passes

Manual Test (local):

Migration

N/A

[changeset-bot]

⚠️ No Changeset found

Latest commit: f2e72ee

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	Sep 5, 2025 2:41pm
catalyst-canary	Ready	Preview	Comment	Sep 5, 2025 2:41pm

3 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
catalyst	Ignored			Sep 5, 2025 2:41pm
catalyst-au	Ignored			Sep 5, 2025 2:41pm
catalyst-uk	Ignored			Sep 5, 2025 2:41pm

[matthewvolk]

@jorgemoya does this allow us to move the entire .open-next folder into .bigcommerce as well? 🤔 I can't remember if these were tied together. If so, we should probably write tests that test across both build and other commands that need this folder.

[jorgemoya]

@matthewvolk Problem I had was running preview: it would look for .open-next where called. I haven't looked to see if that is still the case in the new version.