-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Utility to run local demo #5
Comments
Yeh I was already planning to do this. It shouldn't be that hard.
If you want to see changes, its not hard at all though: just got to
so yeh if you do what I say above you can already rely on the locally built files |
(note what I said above applies specifically to the setup in markdown-it-docutils) |
It would be great to get this in one command that gets a local demo up, watching/rebuilding/reloading, so we don't have to remember/or accidentally commit incorrect things. Have done this a bunch in webpack, I am sure there are simple equivalents in the rollup world. |
oh yeh exactly, I just hadn;t got round to looking yet (plus figuring out how to have the index.html auto-use local scripts vs URL scripts, based on context) |
Although there is obviously nothing stopping you from working it out 😜 |
Right now I believe the process is commenting on/off the local script and just opening this up in any webserver or file://.
It would be great to add a
npm run start
ordev
to bring up a live reloading server on file changes (including styles where appropriate). This is more helpful for the more complicated repos like docutils.This also means the deploy might need to go into a github action (e.g. have done that here), that would allow us to rely on the locally built package rather than the deployed npm package (e.g. not ready to release, but still want the demo updated).
The text was updated successfully, but these errors were encountered: