Automatically closed - issue fixed for 2 weeks with no activity.
- Status changed to Fixed
over 1 year ago 9:29am 30 May 2023
Having only start-storybook --port 3000 will need more work.
When running the command many times for testing changes on the Storybook
Add the kill-port ~2.0 package
Change the Scripts aliases workflow to:
"scripts": {
"theme:init": "webpack --progress --config webpack.config.init.js",
"theme:build": "webpack --progress --config webpack.config.build.js",
"theme:watch": "webpack --progress --config webpack.config.dev.js --watch",
"storybook": "npx kill-port --port 3000; start-storybook --port 3000"
},
rajab@vardot-dev:/var/www/html/products/vartheme_bs5$ yarn storybook
yarn run v1.22.19
$ npx kill-port --port 3000; start-storybook --port 3000
Process on port 3000 killed
info @storybook/react v6.5.15
info
info => Loading presets
info => Serving static files from ././images at /assets
info => Loading custom manager config
info => Using implicit CSS loaders
info => Loading custom manager config
(node:303002) DeprecationWarning: Default PostCSS plugins are deprecated. When switching to '@storybook/addon-postcss',
you will need to add your own plugins, such as 'postcss-flexbugs-fixes' and 'autoprefixer'.
See https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#deprecated-default-postcss-plugins for details.
(Use `node --trace-deprecation ...` to show where the warning was created)
info => Loading custom Webpack config (full-control mode).
10% building 3/7 modules 4 active /var/www/html/products/vartheme_bs5/node_modules/@storybook/core-client/dist/esm/globals/globals.js
info => Using cached manager
webpack built preview 319105f911ca1fb7d412 in 4282ms
╭───────────────────────────────────────────────────╮
│ │
│ Storybook 6.5.15 for React started │
│ 4.54 s for preview │
│ │
│ Local: http://localhost:3000/ │
│ On your network: http://##.##.###.##:3000/ │
│ │
╰───────────────────────────────────────────────────╯
kill-port --port 3000 and then start-storybook --port 3000Fixed
2.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Automatically closed - issue fixed for 2 weeks with no activity.