fix(prerender): allow disabling html sub-folders

[danielroe]

🔗 Linked issue

Related: #1394, #607

❓ Type of change

• 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This PR allows disabling prerendering in subfolders.

It also includes a potential fix for cloudflare pages/vercel presets, which I need to test. (Opening PR in the interim to get feedback on the API/implementation.)

I think safer to merge this first and treat cf/vercel preset issues separately.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[codecov]

Codecov Report

Merging #1676 (f54a0d0) into main (f126cbf) will increase coverage by 0.02%.
The diff coverage is 92.85%.

@@            Coverage Diff             @@
##             main    #1676      +/-   ##
==========================================
+ Coverage   77.78%   77.80%   +0.02%     
==========================================
  Files          76       76              
  Lines        7827     7839      +12     
  Branches      804      805       +1     
==========================================
+ Hits         6088     6099      +11     
- Misses       1737     1738       +1     
  Partials        2        2              

Files Changed	Coverage Δ
src/prerender.ts	85.94% <80.00%> (-0.11%)	⬇️
src/options.ts	97.00% <100.00%> (+0.01%)	⬆️
src/types/nitro.ts	100.00% <100.00%> (ø)

[pi0]

@danielroe I think we can move forward to test on edge directly and revert if any issues before patch release 👍🏼

[atinux]

FYI: 11a2412

Would be nice to think of updating the docs when adding new options 👀

[pi0]

Thanks! And yes we should automate it sometime soon similar to nuxt options...

Also after testing, this option shall be automatically enabled for providers. That's why merged as fix rather than feat.

[atinux]

I don't think we need to automate this as we can just better explain the configuration and it does not take much time to add in docs.

It's just a process we need to get used to.

[pi0]

Without automation it is impossible to not forget and keep docs in sync (with version as well). I plan to do this for the upcming h3 docs as well...

[Hebilicious]

Without automation it is impossible to not forget and keep docs in sync (with version as well). I plan to do this for the upcming h3 docs as well...

Even if we list the existing options in the docs, we should write JSDOC comments to explain what they do (so that its reflected in TS), a lot of the options are not documented anywhere, or just in their implementation PR currently.

[pi0]

@Hebilicious yes true. that's the plan to use jsdocs (similar to nuxt) and automatically extract them to the docs kept in sync :)