Add navigateToChanged option to new dev server
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 109
- Forks
- 20
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
New server works brilliantly.
Opening a new issue as 11ty/eleventy#1305 is closed.
Would it make sense to add an option like navigateToChanged?
When you work on multiple pages/blog posts it comes in very handy if your server and browser just jump to the most recently edited page. (I know Hugo’s server supports such an option.)
Thank you!
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
The issue identifies the new dev server but names no files, tests, or entry points. Start by locating the server's handling of page changes and browser navigation, then define how the navigateToChanged option should behave. Done means the option reliably opens the most recently edited page and has coverage for the requested behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100