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
For frameworks without built in file notifications, a small file should be written in the project output folder, with the changed file path relative to the output folder, as a json array of objects with timestamp and path in the file. The timestamp will be the time at which the event occurred, not the file stat times.
The user can then poll this file for timestamps that differ for their usage, and should not modify the file as the tools will continue to write to it as changes occur.
The text was updated successfully, but these errors were encountered:
For frameworks without built in file notifications, a small file should be written in the project output folder, with the changed file path relative to the output folder, as a json array of objects with
timestamp
andpath
in the file. The timestamp will be the time at which the event occurred, not the file stat times.manifest.changed
=[{ timestamp:11111, path:'assets/image.png'}]
The user can then poll this file for timestamps that differ for their usage, and should not modify the file as the tools will continue to write to it as changes occur.
The text was updated successfully, but these errors were encountered: