This repository has been archived by the owner on Jan 11, 2023. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In production apps, there were still attempts made to
/__webpack_hmr
, which meant that the dev-entry was being included.The short-fix was to modify the build script:
NODE_ENV=production sapper build
... but that's still ugly & not the intended.I added some debuggers and saw that the
dev
block ofcreate_app
was still running. Then took a look at the compiledcli.js
output:The
dev
check is made before manually setting theNODE_ENV
. Also, because of Rollup's "import hoisting" (is that the term?) moving this line to the top of the file, ahead of thedev
import, didn't affect the compiled output.Simply converting
config.dev
toconfig.isDev()
solves this, deferring the check until needed.Now,
sapper build && sapper start
works as expected, while preserving HMR for dev-mode. 🎉