Next.js: Support path aliases when no base url is set

[yannbf]

Closes #11639

What I did

When testing a Nextjs project, I noticed that the path aliases were not working, even though I had them set up correctly.
As of TypeScript 4.1, baseUrl is no longer required, and therefore we shouldn't safeguard against not having it.

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!

This was manually tested in the following scenarios:

• Nextjs + TS + tsconfig with baseUrl set [works]
• Nextjs + TS + tsconfig with no baseUrl set [works]
• Nextjs + JS + jsconfig [works]
• Nextjs + JS + no jsconfig [bails]

1. Run a sandbox for a NextJS template, e.g. yarn task --task sandbox --start-from auto --template nextjs/default-ts
2. Remove baseUrl from tsconfig.json
3. Storybook should still work if components use path aliases

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 d80b2fb. 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 1 target

• nx run-many -t build -c production --parallel=8

---

Sent with 💌 from NxCloud.

[SalahAdDin]

Does this PR solve this issue?

[valentinpalkovic]

No, this is unrelated.