This repository has been archived by the owner on Mar 14, 2024. It is now read-only.
Run eleventy once before starting the server, then watch for changes. #5157
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.
Fixes #3605, unblocks #5008
eleventy --watch
will run eleventy, which means if you have an npm script (like our dev script) where you want to 1st run eleventy, and then watch for changes, you can't really do it without running eleventy twice (issue).The solution is to write our own
chokidar
file watcher (which is what eleventy is using under the hood) to watch thesrc/site
directory and re-run eleventy ourselves. Importantly,chokidar
does not run your command when you first call the npm script.Changes proposed in this pull request:
eleventy --watch
with our own chokidar watcher.