Open antony opened 4 years ago
Looks like the HMR plugin is doing something, since this is in my console:
[HMR] Enabled
sapper-dev-client.js:10 [SAPPER] dev client: bails out in favor of Rollup HMR
...
client.js:237 [HMR] Rebuilding...
client.js:218 [HMR] Apply changes...
client.js:168 [HMR] Up to date
client.js:237 [HMR] Rebuilding...
client.js:218 [HMR] Apply changes...
client.js:168 [HMR] Up to date
But I'm definitely getting full reloads, still.
Browserslist: caniuse-lite is outdated. Please run next command
npm update
✔ client (1m03s) ✔ server (1m03s)Listening on http://localhost:1234 ✔ service worker (91ms)
Apologies for the off-topic question. I've been searching Google for anything involving a similar notification you received above:
Browserslist: caniuse-lite is outdated. Please run: npx browserslist@latest --update-db
I know Sapper is currently not being updated, however is this Browserlist update something I need to be concerned about or shall I just ignore it? Thanks for any insight.
So, apologies for the next bug report, since it's another mystery one.
I run my Sapper app on a custom port (1234), by passing in the
PORT
variable.However, it would seem that using the HMR plugin + config, I get
port in use
errors and my server immediately crashes. I'm still investigating why, and will update if I find any useful information.Noteworthy is that if I modify
server.js
afterwards causing it to recompile, the server does seem to start-up successfully (whether it works is another matter).