-
-
Notifications
You must be signed in to change notification settings - Fork 127
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
Repeat to connect to the server #687
Comments
I don't understand this - the repro steps listen explicitly that the package.json should be modified - so yes, with such a modification the server should restart. I'll have a look with the repro steps, but a server restart is expected if certain files changed (otherwise you'd need to manually shut down the server and restart it again). |
Alright, so as this is an edge case (package.json changed, leading to a change for the dev server) we'll exclude it. This implies that changes to the package.json that affect the build (e.g., change of the "app" path) would require a fixed restart. I guess this is a good trade-off, as such scenarios rarely occur and often are expected to come with a manual server restart anyway. The server would still restart on changes to the krasrc; as it might re-configure the server in crucial areas. |
Hm these two are not connected; also I have not seen this myself. I guess we can close it unless you can come up with a reproducible. |
Bug Report
For more information, see the
CONTRIBUTING
guide.Prerequisites
Environment Details and Version
macos
[email protected]
Description
Repeat to connect to the server
Steps to Reproduce
MWE
yarn && cd src/samples/sample-piral-core && yarn start
src/samples/sample-piral-core/package.json
and commit to the staging areaExpected behavior
Do not restart the server repeatedly
Actual behavior
Repeatedly restart the server
Possible Origin/Solution
The content of the files
package.json/.krasrc
monitored by fs.watch has not changed, and the server has been restarted.The text was updated successfully, but these errors were encountered: