Start script + watchers need to be more verbose
See original GitHub issueFile in Question https://github.com/contiamo/operational-ui/blob/a432c8e90277345b31e11ec30fb02599ddaf7e77/scripts/start.ts#L1-L137
Currently, yarn start
doesn’t really output errors (probably because styleguidist reports errors on something other than stderr
). As a result, errors are swallowed and we just see infinite spinners.
More context in this issue.
Let’s fix this by reporting and even process.exit(1)
ing when styleguidist fails.
Issue Analytics
- State:
- Created 4 years ago
- Comments:17 (9 by maintainers)
Top Results From Across the Web
How can I run multiple npm scripts in parallel?
A quick way of doing it is npm run start-watch & npm run wp-server . This will run the first command as a...
Read more >npm-watch
run scripts from package.json when files change. Latest version: 0.11.0, ... Start using npm-watch in your project by running `npm i npm-watch`.
Read more >bahmutov/start-server-and-test
This command is meant to be used with NPM script commands. If you have a "start server", and "test" script names for example,...
Read more >Develop ASP.NET Core apps using a file watcher
This tutorial demonstrates how to install and use the .NET Core CLI's file watcher (dotnet watch) tool in an ASP.NET Core app.
Read more >CLI options
Storybook comes with two CLI utilities: start-storybook and build-storybook . ... (Optional with --https, required if using a self-signed certificate)
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It succeeds in your case! This is great! It fails in other cases. I think a good option is to explicity create a styleguidist error (have odd syntax in one of the
src
components) and then try to start the dev server. This should fail, and you likely won’t be able to see an error. This is what we’re trying to fix. 😄sorry for the long delays Yes, I’ve read your comment, the plan is to reject the promise and halt the spinner when the error occurs. There is something I haven’t quite figured out about the issue with styleguidist and I’m hoping I’ll play around for a while before I have a concrete understanding of it, shouldn’t take long