gajus / gajus/approximate-now

API access differs from that of Date

Open
#2 3 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
TypeScript
Stars
22
Forks
2
PR merge metrics
No merged PRs in 30d

Description

Is it intentional for the package's API access to differ from that of Date? I initially expected the package to work as a drop-in replacement of `Date.now()` by exporting a function by the name of `now()` rather than an object with a property by the name of `now`.

Is this something you'd allow a PR to change? I have a branch with performance increases adding up to a little over 100%. I'd like to create a PR for it but it's based on an API refactor that would close this issue.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.