Skip to content

Conversation

@hansmannj
Copy link

@hansmannj hansmannj commented Dec 12, 2025

It is now possible to pass an optional filename argument for specifying the name of the presentation html file. If no argument is passed, the default behavior is the same, i.e. open index.html. If started with npm start -- --file=presentation.html then the file presentation.html is served. This file might be located in a different directory. Makes it easy to store separate presentations in another directory or even repository.

It is now possible to pass an optional filename argument for specifying
the name of the presentation html file. If no argument is passed, the
default behavior is the same, i.e. open index.html.
If started with npm start -- --file=presentation.html then the file
presentation.html is served. This file might be located in a different
directory. Makes it easy to store separate presentations in another directory
or even repository.
@hansmannj
Copy link
Author

Hi @hakimel and all contributors. Thanks a lot for this very nice piece of software 🥇
I like it a lot and just wanted to suggest addind something similar to what I drafted in this PR.
I'd like to store all my presentation's HTML file in a separate folder, which is also another repository.
Allowing to pass the presentation's filename, I can keep things nicely separated and clean.
What's your take on this?

Using process.cwd() as the server root to correctly handle external presentation files.
@hansmannj hansmannj changed the title This commit allows the user to pass an optional filename argument This PR allows the user to pass an optional filename argument Dec 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant