This repository has been archived by the owner on Oct 16, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 230
Question: can generate outputs for all files on npm start
only, and not every time a file is edited?
#124
Comments
I reckon you should look into the |
Thanks Andy. I did as you said, and it works but it doesn't: even though it didn't regenerate all the other pages, the time it takes to reload the browser was actually the same! Check the log. With the normal behavior, it takes 8.44 seconds to do a change:
Using
Any idea? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have close to 50 blog posts in my Hylia site currently. When I write a new blog post, I first launch the development server with
npm start
, which takes some time to build the whole site... that is ok. However, it also builds the whole site whenever I edit the blog post, making the experience a bit slow.I understand that different pages may be affected (such as if I add a new tag) and they need be rebuilt, but I really don't care about those other pages, only about the blog post being edited.
So, is it possible to tell Hylia to only regenerate the page that has changed? (Even if the state of the site will be inconsistent... I don't care about that, it's my local setup, and I can always run
npm start
again)Thanks
The text was updated successfully, but these errors were encountered: