Closed carvinlo closed 7 months ago
The content of the files package.json/.krasrc monitored by fs.watch has not changed, and the server has been restarted.
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.
The server would restart multiple times on changes to the krasrc. version: 1.5.4-beta.6998
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.
The server would restart multiple times on changes to the krasrc. version: 1.5.4-beta.6998
This is also an edge case. This happens when app-shell's webpack.config.js configures a longer build. But it no longer affects normal development. Thanks for the quick fix.
Bug Report
For more information, see the
CONTRIBUTING
guide.Prerequisites
Environment Details and Version
macos node@18.20.1
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.