-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No such file or directory for storybook-init-framework-entry.js, preview.js-generated-config-entry.js and generated-stories-entry.js #12864
Comments
Did you try removing If that doesn't work, try removing |
@Noldaru your webpack config uses the |
Looks like the same issue as #9515, which was closed due to lack of activity. As mentioned in this issue, a problem with As a workaround you may try to apply |
Thanks for the workaround @fesor. Do you have a code snippet you can share? |
The workaround of excluding import {TsconfigPathsPlugin} from 'tsconfig-paths-webpack-plugin';
function webpackFinal(config, {configType}) => {
const threadLoader = {
loader: 'thread-loader',
options: {
poolTimeout: 500,
workers: os.cpus().length,
name: 'ts-pool',
},
};
const tsLoader = {
loader: 'ts-loader',
options: {
configFile: 'tsconfig.json',
transpileOnly: true,
happyPackMode: true,
onlyCompileBundledFiles: true,
experimentalFileCaching: true,
compilerOptions: {
module: 'esnext',
},
}
};
// Exclude .storybook from thread-loader
config.module.rules = [
{
include: [/\.storybook/],
exclude: [/node_modules/],
test: /\.[jt]s(x?)$/,
use: [
tsLoader,
],
},
{
exclude: [/node_modules/, /\.storybook/],
test: /\.[jt]s(x?)$/,
use: [
threadLoader,
tsLoader,
],
},
]
config.plugins = [
...(config.plugins ?? []),
new webpack.ProvidePlugin({
Buffer: ['buffer', 'Buffer'],
process: 'process/browser',
}),
];
config.resolve.plugins = [
new TsconfigPathsPlugin({
configFile: path.resolve(__dirname, '../tsconfig.json'),
}),
];
config.resolve.symlinks = false;
return config;
} |
Running into the exact same issue, it works fine when running Here's a repo that has the issue happening: https://github.com/LanFeusT23/vue3-storybook-test
|
@LanFeusT23 You can try exclude module.exports = {
chainWebpack: config => {
config.module.rule('js')
.exclude
.add(/\.storybook/)
.end()
.end()
}
} |
Hi guys, mine running default and upgrade from 6.0 to 6.4, still facing the same error. Didnt set the thread loader in webpack, but still no work. |
Workaround: use this on your
|
This issue got stale. We did a lot of refactoring and optimizations in Storybook 7, and even the RC release of Storybook 8 is around the corner. Please try out the latest prerelease version of Storybook ( |
[Support] No such file or directory error for unknown config files on build
I am attempting to upgrade from storybook version 5.2 to 6.x, but am getting several errors for files that do no exist in my
.storybook
folder after the build, namelystorybook-init-framework-entry.js
,preview.js-generated-config-entry.js
andgenerated-stories-entry.js
I can find no reference to any of these files nor make out their purpose in the documentation, nor was I able to find any other issues involving missing config files.
Steps to reproduce
Update storybook
Attempt to build storybook:
Please specify which version of Storybook and optionally any affected addons that you're running
Other libraries
Affected platforms
Platform: Windows 10
Node version: 12.13.0
NPM version: 6.14.8
Screenshots / Screencast / Code Snippets (Optional)
Errors
./storybook/main.js
./storybook/manager.js
.storybook/preview.js
.storybook/webpack.config.js
Other notes
This is a JavaScript turned TypeScript project, so we are temporarily using babel to transpile TS, in order to prevent the build from failing on every type error. The project is quite large, so fixing them all is quite frankly an ongoing mammoth task.
The text was updated successfully, but these errors were encountered: