Next.js: Add experimental SWC support

[valentinpalkovic]

Closes #24827

What I did

Added experimental SWC mode for Next.js >= 14

Checklist for Contributors

Testing

The changes in this PR are covered in the following automated tests:

• stories
• unit tests
• integration tests
• end-to-end tests

Manual testing

This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!

Next.js 12 sandbox

-> Setting framework.options.builder.useSWC: true shouldn't have any effect. Instead the user should get a warning in the console, that SWC mode is only supported in Next.js v14 and above. It would be beneficial also to test Next.js 13, since we currently don't have a Next.js 13 sandbox in place. Just check out one of the Next.js sandboxes and change the next dependency to the latest v13. The behaviour should be the same as for Next.js v12. SWC is not supported here. Storybook should work as expected in Babel mode.

Other Next.js sandboxes

-> Set framework.options.builder.useSWC: true and test whether all Next.js Stories are working as expected. Personally, I have tested the local font option already.

Documentation

• Add or update documentation reflecting your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Checklist for Maintainers

• When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli/src/sandbox-templates.ts

• Make sure this PR contains one of the labels below:

  Available labels

  • bug: Internal changes that fixes incorrect behavior.
  • maintenance: User-facing maintenance tasks.
  • dependencies: Upgrading (sometimes downgrading) dependencies.
  • build: Internal-facing build tooling & test updates. Will not show up in release changelog.
  • cleanup: Minor cleanup style change. Will not show up in release changelog.
  • documentation: Documentation only changes. Will not show up in release changelog.
  • feature request: Introducing a new feature.
  • BREAKING CHANGE: Changes that break compatibility in some way with current major version.
  • other: Changes that don't fit in the above categories.

🦋 Canary release

This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the @storybookjs/core team here.

core team members can create a canary release here or locally with gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=<PR_NUMBER>

[socket-security]

Updated dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
next	14.0.0...14.0.2	None	+10/-10	1.14 GB	vercel-release-bot
@types/jscodeshift	0.11.7...0.11.10	None	+0/-0	37.9 kB	types

[jonniebigodes]

@valentinpalkovic thanks for taking the time to put together this pull request and include the required changes to the documentation. Appreciate it 🙏 ! Only one small thing for you to look into and this should be good to go from my end. Approving this to unblock you.

[yannbf]

Suggested change

	import { NextjsSWCNotSupportedError } from 'lib/core-events/src/errors/server-errors';
	import { NextjsSWCNotSupportedError } from '@storybook/core-events/server-errors';