-
-
Notifications
You must be signed in to change notification settings - Fork 231
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
Add onDTSSuccess option #1024
base: main
Are you sure you want to change the base?
Add onDTSSuccess option #1024
Conversation
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
Personally would expect the fix and desired behavior to be onSuccess
to be called once the command (build+dts) has completed. I think there is very little use of having callback for success DTS separate from the build success callback.
In addition to this there is no guarantee that DTS will finish after the builds
Line 408 in 690af7b
await Promise.all([dtsTask(), mainTasks()]) |
This makes it quite unreliable even so simple cases like "copy all files when the whole build step is completed"
@ToTeTo i think my comment on the linked fixed issue is a pretty compelling use case:
maybe this pr doesnt completely fix #700 though because there are other use cases |
115a451
to
57654f6
Compare
Fixes #700