Next.js: Fix next/font usage on Windows machines

[valentinpalkovic]

Closes #26450, closes #26699

What I did

next/local/font or next/google/font weren't usable on Windows machines. This is now fixed.

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!

1. Run the nextjs/default-js sandbox locally on a Windows machine
2. Visit the Font story and verify it properly displays the Google font
3. Adjust your .storybook/main.js and add the following setting:

staticDirs: [
    '..\\public',
+    {
+      from: '../src/stories/frameworks/nextjs_nextjs-default-js',
+      to: 'src/stories/frameworks/nextjs_nextjs-default-js',
    },
  ],
4. Start Storybook and verify the local font gets properly displayed in the `Font` story.

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>

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit e40d784. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 2 targets

• nx affected -t check -c production --parallel=7
• nx run-many -t build -c production --parallel=3

---

Sent with 💌 from NxCloud.

[sdandrader]

Hi Valentine.
I see that some checks were not succesful. ¿When this fix will be available on the last release? Thanks!

[valentinpalkovic]

Hi @sdandrader,

I plan to release this fix tomorrow (8.0.6).