-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
🚑 Hotfix: Use chokidar to watch only for conf.yml changes #1496
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
✅ Deploy Preview for dashy-dev ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems good to me for a hotfix, however with this all the problems like favicon, pages and so more, that should have been fixed with this release probably wouldn't be fixed anymore? Or only on a CT reboot.
They'll still be fixed. This just updates how the app is re-built when changes happen. Previously it was rebuilding whenever there was any change. I guess that was the issue causing the loop. I tried using I've just written a script that watches config for changes, and triggers a re-build. Testing it now. But hopefully that removes the need for an extra dependency, while also fixing all the issues which needed a rebuild. Testing atm..... |
Love that idea!
Quickly looked over it, looks very good!
👍 |
Category: Hotfix
Overview
Useschokidar
to watch only for whenconf.yml
changes.Uses a custom script (here) to watch for changes (only in
conf.yml
), and trigger a rebuild. Includes comparing hash of previous file with current one to prevent successive changes, as well as a debounce limit of 5000ms, and some logging.Issue Number #1494
New Vars N/A
Screenshot N/A
Code Quality Checklist (Please complete)