Option to output "pretty" HTML paths
See original GitHub issueMany static site generators enable you to output so-called “pretty” HTML paths, i.e. instead of /about.html
they produce /about/index.html
. I’ve been using iles a fair amount recently and haven’t found a way to do this. If i"m mistaken, please let me know! Otherwise, this would be very nice to have, and I’d be happy to contribute this if you can provide some pointers on the best way to do so (i.e. should this be a Vite plugin? An iles plugin? Something built into iles?).
Issue Analytics
- State:
- Created 10 months ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
How can I get Express to output nicely formatted HTML?
In your main app.js or what is in it's place: Express 4.x if (app.get('env') === 'development') { app.locals.pretty = true; }. Express 3.x...
Read more >Understanding HTML File Paths & How to Use Them
To make use of HTML file paths, the two options are either relative or absolute file paths. With relative file paths, the files...
Read more >How to make html files output to a different directory · Issue #665
If you need to output html to a separate directory, in my case outside the dist directory, you can do filename: '../index.html' for...
Read more >HTML Options - Quarto
For HTML output, sets the base CSS font-size property. For LaTeX and ConTeXt output, sets the font size for the document body text....
Read more >Output - webpack
This option determines the name of each output bundle. The bundle is written to the directory specified by the output.path option. For a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@ElMassimo Personally, I prefer (and recommend!) separate link checks for internal and external links (which htmltest supports). To me, checking internal links is very much an every-single-PR thing whereas external link checks shouldn’t make a PR fail (because they’re dependent on factors outside your project). Lychee is great for external links but AFAICT can’t do internal or external only on a specific run. Anyhoo, not suggesting this approach is for everyone, just explaining my reasoning 😄
This can break PWA here, maybe we can protect against providing custom
manifestTransform
: it is working this way for example SvelteKit pwa integration: