Lage touches every file... why? #720
Unanswered
kensternberg-authentik
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
["^build"]
admin-overview: "*"
listed inpackage.json
.Two things:
Whenever I change something, Lage detects the change and the build runs correctly, with only the changed package and its dependencies being rebuilt. But if I change it back, Lage does not recognize that change and will not rebuild the package. I have to issue
--no-cache
to make it work. (I'm kinda expecting this to work likeMake
; if I touch a dependent file, it ought to trigger a build!)Whenever I run Lage at all, even if it reports "success: 0, skipped: 20", my IDE's console reports:
Which is every tab I have open. The documentation for my IDE says: "If the visited file name matches and the file has changed on disk but the open buffer is not modified, then the file is re-read from disk without asking the user for confirmation."
While that's probably a mark against my IDE of choice (yes, Emacs), but what the heck is Lage doing that it's touching/changing every dependent file!?
Beta Was this translation helpful? Give feedback.
All reactions