After updating to Storybook 10 (with Angular), compilation crash with: import_meta.resolve is not a function

[JeanRemiDelteil]

I was not able to run Storybook in my project after upgrading to v10.x. It was running fine in 9.x.
It's an Angular project, using @storybook/angular.

I tried all those different combinations:
Storybook: 10.1.0-beta.4, and 10.0.8
Angular: 20.x, and 21.x
Node 22.21.1, and 24.11.1

Here is the whole error from the logs:

[error] TypeError: import_meta.resolve is not a function
    at importMetaResolve (/home/<project>/node_modules/storybook/dist/_node-chunks/chunk-NORFPLB6.js:717:48)
    at resolvePackageDir (/home/<project>/node_modules/storybook/dist/_node-chunks/chunk-NORFPLB6.js:721:35)
    at logger2 (/home/<project>/node_modules/storybook/dist/_node-chunks/chunk-KI6KY2ZN.js:53:3)
    at Object.<anonymous> (/home/<project>/node_modules/storybook/dist/_node-chunks/chunk-KI6KY2ZN.js:287:30)
    at Module._compile (node:internal/modules/cjs/loader:1761:14)
    at Object.transformer (/home<project>/node_modules/tsx/dist/register-D46fvsV_.cjs:3:1104)
    at Module.load (node:internal/modules/cjs/loader:1481:32)
    at Module._load (node:internal/modules/cjs/loader:1300:12)
    at TracingChannel.traceSync (node:diagnostics_channel:328:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:245:24)

This is the code involved in the browser chunk:

var importMetaResolve = (...args) => typeof import.meta.resolve != "function" && process.env.VITEST === "true" ? (console.warn(
  "importMetaResolve from within Storybook is being used in a Vitest test, but it shouldn't be. Please report this at https://github.com/storybookjs/storybook/issues/new?template=bug_report.yml"
), pathToFileURL2(args[0]).href) : import.meta.resolve(...args), resolvePackageDir = (pkg, parent) => {
  try {
    return dirname(fileURLToPath2(importMetaResolve(join(pkg, "package.json"), parent)));
  } catch {
    return dirname(fileURLToPath2(importMetaResolve(join(pkg, "package.json"))));
  }
}, isTypescriptLoaderRegistered = !1;

I tried to replicate this, but in another Angular project it ran without any issues.
If anybody has an idea as to a possible cause !?

[dosubot[bot]]

Hi @JeanRemiDelteil! I'm Dosu and I’m helping the storybook team.

Storybook 10 switched to ESM-only and now uses import.meta.resolve for module resolution, which only works if your config files and environment are fully ESM-compliant. This error usually means Storybook is running in a CommonJS context or your .storybook/main.* or custom preset files are not valid ESM modules. Even if your Node version is new enough, any CJS config or extensionless import can break things cite cite.

Here’s what to check:

• Make sure .storybook/main.* and any custom preset files are ESM (use .js, .mjs, or .ts, and use export default, not module.exports).
• If you have any extensionless relative imports in config or presets, add the full file extension (e.g., import x from './file.js') cite.
• If you have custom addons or presets, ensure they’re also ESM and not using require or CJS patterns.
• If you haven’t already, run Storybook’s automigrate/migration scripts to update config patterns to ESM and fileURLToPath(import.meta.resolve(...)) cite.
• Compare your working and non-working projects’ .storybook configs and presets for any CJS usage or missing extensions.

If you update your configs and still see the error, check for any dependencies or scripts that might be running Storybook in a CJS context. Let me know if you want a checklist or example config!

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[JeanRemiDelteil]

After further investigation and tests, nothing in the Storybook configuration or code had any leverage on this issue.
It was caused by a configuration or a cache issue (probably) in Jetbrains IDE.
Deleting the .idea/ folder solved the issue...