fix: use a proper way to set Timestamp param #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
problems:
It should be 'HH'.
dayjsmodule is the only used here, there's a simpler way to present the whole acceptable Timestamp string:(new Date()).toISOString(), then remove the millisecond part by.replace(/\.\d{3}Z$/, '').So I removed this dependency, and use
(new Date()).toISOString().replace(/\.\d{3}Z$/, 'Z')here.by the way:
when I run
npm run build, there're other files and directories has been changed local on my disk, but I've just pick the files about I've modified to push.Maybe the whole npm package should be upgraded completely by you, the maintainers. :-)