You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received an instance of Array
at __node_internal_captureLargerStackTrace (node:internal/errors:496:5)
at new NodeError (node:internal/errors:405:5)
at validateString (node:internal/validators:162:11)
at Object.join (node:path:1175:7)
at loadTsconfig (./node_modules/esbuild-register/dist/node.js:4232:37)
at loadSyncDefault (./node_modules/esbuild-register/dist/node.js:4178:18)
at tsConfigLoader (./node_modules/esbuild-register/dist/node.js:4165:22)
at configLoader (./node_modules/esbuild-register/dist/node.js:4493:22)
at loadConfig2 (./node_modules/esbuild-register/dist/node.js:4476:12)
at registerTsconfigPaths (./node_modules/esbuild-register/dist/node.js:4752:67)
at register (./node_modules/esbuild-register/dist/node.js:4884:35)
at interopRequireDefault (./node_modules/@storybook/core-common/dist/index.js:32:3142)
at serverRequire (./node_modules/@storybook/core-common/dist/index.js:37:373)
at loadMainConfig (./node_modules/@storybook/core-common/dist/index.js:50:6889)
at async buildDevStandalone (./node_modules/@storybook/core-server/dist/index.js:116:1244)
at async withTelemetry (./node_modules/@storybook/core-server/dist/index.js:101:4155)
at async dev (./node_modules/@storybook/cli/dist/generate.js:502:401)
at async Command.<anonymous> (./node_modules/@storybook/cli/dist/generate.js:504:225)
WARN Broken build, fix the error above.
WARN You may need to refresh the browser.
Describe the bug
TypeScript5.0 provides the ability to extend from multiple configs at once.
https://devblogs.microsoft.com/typescript/announcing-typescript-5-0-rc/#supporting-multiple-configuration-files-in-extends
But Storybook throw error on using this.
To Reproduce
https://stackblitz.com/edit/github-jrbz2p?file=tsconfig.json
System
Additional context
No response
The text was updated successfully, but these errors were encountered: