In user code, the return type undefined() from the progress callback causes a TypeScript error Type void is not assignable to type undefined. To avoid this error the user has to explicitly return undefined; in their progress implementation which does not make much sense.
This PR changes undefined() to void() to avoid this TS error.
Also, I've added an optional ? in the changelog create script to have a better error message if a user forgets to provide the changelog name as an argument. Without it, it will try to call replace on undefined with a not very helpful error message.
In user code, the return type
undefined()from the progress callback causes a TypeScript errorType void is not assignable to type undefined. To avoid this error the user has to explicitlyreturn undefined;in theirprogressimplementation which does not make much sense.This PR changes
undefined()tovoid()to avoid this TS error.Also, I've added an optional
?in the changelog create script to have a better error message if a user forgets to provide the changelog name as an argument. Without it, it will try to callreplaceonundefinedwith a not very helpful error message.