You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The reason this is the case, is because when editing a file in /pages, we know which template/page we need to compile (which is what will trigger the refresh). If making changes to a partial or layout, we don't know which page we are currently working on, so we would have to re-compile every template available. The project I initially built this for had over 100 templates - compiling all these templates every time I changed a partial/layout proved to be inefficient.
This is a valid issue, though. You should be able to make a change to a partial or layout and trigger a refresh on the page you're working on - I'm sure it is possible, will just need further investigation.
I note this when coding. The same occurs with images folder, putting new images in this folder don't run the images task to copy to dist. But even so, Noah is being very helpful to me.
Thanks for the feedback @jklemm, it is much appreciated. I will happily accept pull requests whilst I'm working on my other project, One-Nexus. Otherwise I will be coming back to work on Noah in the near future :)
After running
npm run serve
Only updates to /pages trigger a reload which can be annoying when you're working in the /partials or /layouts folder.
Running
npm run build
triggers a build which refreshes the browser. One extra step.The text was updated successfully, but these errors were encountered: