Entering `rs` in redwood dev server terminal does nothing (does not restart)
See original GitHub issueSupposedly, one can restart the redwood dev server at any time by typing <kbd>rs</kbd> in the terminal currently executing yarn rw dev
:
However, nothing happens when i do as advised by that message.
It’s not like i ever had to rely on restarting so far, the redwood server dev-server turns out to be very resilient – in stark contrast to the storybook server (where autorefresh misses any updates to theme customizations and it needs to be completely restarted whenever the addons-config is changed) – but i wanted to report this, so either the advice can be removed or this can be fixed.
Issue Analytics
- State:
- Created a year ago
- Comments:9 (8 by maintainers)
Top Results From Across the Web
Command Line Interface | RedwoodJS Docs
The following is a comprehensive reference of the Redwood CLI. You can get a glimpse of all the commands by scrolling the aside...
Read more >ts-node-dev not restarting when changes made - Stack Overflow
When I do any changes, I get the little popup, but it doesn't actually restart the server not sure what I am doing...
Read more >VSI OpenVMS TCP/IP User's Guide - VMS Software, Inc.
This document describes how to use the VSI TCP/IP user commands. Included are easy to follow instructions for beginning users and command pages...
Read more >Beginners Guide to Oracle VM Server for SPARC
Enable the Virtual Network Terminal Server Daemon . ... This guide does not require prior Solaris™ Operating ... {0} ok boot -rs. Take...
Read more >Administration Guide - GlassFish Server Open Source Edition
Corporation and its affiliates will not be responsible for any loss, costs, ... Configuring a DAS or a GlassFish Server Instance for Automatic...
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
I tried nodemon with
--quiet
option and I like it ! I don’t think we need nodemon output.From their wiki : “Minimise nodemon messages to start/stop only.”
I tried to reproduce as many type of error I can and the error output works, but I don’t know what kind of specific error for nodemon I can reproduce to see what happen.
Yeah, that output is meaningless in the context of
rw dev
. What would happen if we just suppressed nodemon default output. Don’t we just need to know state, e.g. “started”, “error”, “stopped”?