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
I could potentially provide this information. But just so you know, this information is only intended for debugging esbuild's watch mode itself. It consists of a single path and represents the first "thing" that watch mode found that triggered the rebuild, for esbuild's internal representation of "thing." For example, if the number of directory entries changed and esbuild's previous build needed to iterate over the files of that directory, then the "thing" is the directory. It does not represent the changed files at all. And even if the "thing" is a file instead of a directory, watch mode starts the new build as soon as it detects a single difference. It does not continue checking all of the files in the previous build to see what files have changed. So what you are asking for may actually not be what you wanted.
In fact, this requirement comes from obsessive-compulsive disorder. I created a semantic log package for a more beautiful console with esbuild.
I don't know the GO language, otherwise I would PR to optimize the log 😂
Not sure if the following is the fastest solution for existing architectures, and you don't need to care about the rationale, just mark it with --log-level
esbuild config:
Output result:
I don't see any meta for file changes, so I can't print out the changes.
It's accessible within esbuild itself.
esbuild src/index.ts --log-level=info
The text was updated successfully, but these errors were encountered: