Error-out on failure with `eleventy --serve`
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 109
- Forks
- 20
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
Since eleventy --serve continues to attempt to generate output and does not error-out on failures, I'm often confused by how my changes don't seem to reflect in the output. I use hotel, which displays a clear error message in the browser when attempting to access the site after the server crashes with an non-zero error code.
Having eleventy --serve error-out on failure (at least by default) would be awesome.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how eleventy --serve handles generation failures and how the server process reports its exit status. Compare the current behavior with the requested default failure behavior, then verify that a failed generation stops serving and follows the expected non-zero error path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli, devtools
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100