With v1.72, Exolve might scale up grids to better fill available width. In case this looks weird for your grids, there's a way to turn it off (but I would appreciate learning about such problems to see if I can do something better).
Here's the full CHANGELOG entry:
Version: Exolve v1.72: August 9, 2026 - Scale up the grid to fill available width. The need for this became clearer to me (sadly) only after I switched my laptop to one with a wider screen.
- We try to use 2/5th of the available width for the grid and the remaining for two clue columns.
- We now always respond to window-resizing (previously we only acted if a big enough change happened). But we throttle the response, waiting 300ms to accumulate any ongoing resizing.
- The scaling up is done upto a limit (max cell width 64).
- The scaling up is not done in the following cases:
- It's a "temp" puzzle (which stops this behaviour in Exet too).
- The user has passed a customizer function.
- The user has specified offsetLeft/grid-bounds.
- There ae shaped cells.
- It's a 3d grid.
- Add exolve-options scale-up-grid:always and scale-up-grid:never to override the above resttrictions (with always) or to simply avoid scaling up (never).
- Some other minor tweaks: numberSize is not limited to a max font size, we assume all of the window width is available if the parentElement is root (or its parent is root), not worrying about a scrollbar (i.e., we use window.innerWidth rather than document.documentElement.clientWidth). This avoids the otherwise inconsistent behaviour between the first load and subsequent resizing arriving at the same size.
- Viresh