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 am currently using tsup with a tsup.config.ts.
This config file dynamically finds the target entry files because the logic behind it is too complex for globber matching.
When using tsup --watch however, it seems like the config is not reloaded on file updates, thus making it so that new files are not considered as possible entry files, and the watch process has to be restarted to include them.
Ideally, I could set some config option that makes it so that the config script is re-executed whenever watch mode detects an update.
Alternatively you could declare this as out-of-scope and I will simply have to use some third party watch-runner for this.
Thank you for your time either way.
Upvote & Fund
We're using Polar.sh so you can upvote and help fund this issue.
We receive the funding once the issue is completed & confirmed by you.
Thank you in advance for helping prioritize & fund our backlog.
The text was updated successfully, but these errors were encountered:
I am currently using
tsup
with atsup.config.ts
.This config file dynamically finds the target entry files because the logic behind it is too complex for globber matching.
When using
tsup --watch
however, it seems like the config is not reloaded on file updates, thus making it so that new files are not considered as possible entry files, and the watch process has to be restarted to include them.Ideally, I could set some config option that makes it so that the config script is re-executed whenever watch mode detects an update.
Alternatively you could declare this as out-of-scope and I will simply have to use some third party watch-runner for this.
Thank you for your time either way.
Upvote & Fund
The text was updated successfully, but these errors were encountered: