Gathering detailed insights and metrics for d3-time
A calculator for humanity’s peculiar conventions of time.
Installations
npm install d3-timeDeveloper Guide
BETA
Typescript
No
Module System
ESM
Min. Node Version
>=12
Node Version
18.12.1
NPM Version
8.19.2
Score
99.6
Supply Chain
100
Quality
78.3
Maintenance
100
Vulnerability
100
License
Releases
36
Contributors
8
Unable to fetch Contributors
Languages
2
JavaScript
Shell
JavaScript (95.36%)
Shell (4.64%)
Developer
Download Statistics
Total Downloads
1,180,902,143
Last Day
1,645,811
Last Week
7,210,325
Last Month
31,527,997
Last Year
366,558,377
GitHub Statistics
233 Stars
221 Commits
56 Forks
13 Watching
4 Branches
8 Contributors
Bundle Size
8.62 kB
Minified
2.46 kB
Minified + Gzipped
Maintainers
2
Package Meta Information
Latest Version
3.1.0
Package Id
d3-time@3.1.0
Unpacked Size
62.97 kB
Size
13.23 kB
File Count
17
NPM Version
8.19.2
Node Version
18.12.1
Total Downloads
Cumulative downloads
Total Downloads
1,180,902,143
Last day
-2.2%
1,645,811
Compared to previous day
Last week
-12.7%
7,210,325
Compared to previous week
Last month
7.2%
31,527,997
Compared to previous month
Last year
30.7%
366,558,377
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dependencies
1
Dev Dependencies
4
Versions
d3-time
When visualizing time series data, analyzing temporal patterns, or working with time in general, the irregularities of conventional time units quickly become apparent. In the Gregorian calendar, for example, most months have 31 days but some have 28, 29 or 30; most years have 365 days but leap years have 366; and with daylight saving, most days have 24 hours but some have 23 or 25. Adding to complexity, daylight saving conventions vary around the world.
As a result of these temporal peculiarities, it can be difficult to perform seemingly-trivial tasks. For example, if you want to compute the number of days that have passed between two dates, you can’t simply subtract and divide by 24 hours (86,400,000 ms):
1start = new Date(2015, 02, 01) // 2015-03-01T00:00 2end = new Date(2015, 03, 01) // 2015-04-01T00:00 3(end - start) / 864e5 // 30.958333333333332, oops! 🤯
You can, however, use d3.timeDay.count:
1d3.timeDay.count(start, end) // 31 😌The day interval is one of several provided by d3-time. Each interval represents a conventional unit of time—hours, weeks, months, etc.—and has methods to calculate boundary dates. For example, d3.timeDay computes midnight (typically 12:00 AM local time) of the corresponding day. In addition to rounding and counting, intervals can also be used to generate arrays of boundary dates. For example, to compute each Sunday in the current month:
1start = d3.timeMonth.floor() // 2015-01-01T00:00 2stop = d3.timeMonth.ceil() // 2015-02-01T00:00 3d3.timeWeek.range(start, stop) // [2015-01-07T00:00, 2015-01-14T00:00, 2015-01-21T00:00, 2015-01-28T00:00]
The d3-time module does not implement its own calendaring system; it merely implements a convenient API for calendar math on top of ECMAScript Date. Thus, it ignores leap seconds and can only work with the local time zone and Coordinated Universal Time (UTC).
This module is used by D3’s time scales to generate sensible ticks, by D3’s time format, and can also be used directly to do things like calendar layouts.
Installing
If you use npm, npm install d3-time. You can also download the latest release on GitHub. For vanilla HTML in modern browsers, import d3-time from Skypack:
1<script type="module"> 2 3import {timeDay} from "https://cdn.skypack.dev/d3-time@3"; 4 5const day = timeDay(); 6 7</script>
For legacy environments, you can load d3-time’s UMD bundle from an npm-based CDN such as jsDelivr; a d3 global is exported:
1<script src="https://cdn.jsdelivr.net/npm/d3-array@3"></script> 2<script src="https://cdn.jsdelivr.net/npm/d3-time@3"></script> 3<script> 4 5const day = d3.timeDay(); 6 7</script>
API Reference
Equivalent to interval.floor, except if date is not specified, it defaults to the current time. For example, d3.timeYear(date) and d3.timeYear.floor(date) are equivalent.
1monday = d3.timeMonday() // the latest preceeding Monday, local time
# interval.floor(date) · Source
Returns a new date representing the latest interval boundary date before or equal to date. For example, d3.timeDay.floor(date) typically returns 12:00 AM local time on the given date.
This method is idempotent: if the specified date is already floored to the current interval, a new date with an identical time is returned. Furthermore, the returned date is the minimum expressible value of the associated interval, such that interval.floor(interval.floor(date) - 1) returns the preceeding interval boundary date.
Note that the == and === operators do not compare by value with Date objects, and thus you cannot use them to tell whether the specified date has already been floored. Instead, coerce to a number and then compare:
1// Returns true if the specified date is a day boundary.
2function isDay(date) {
3 return +d3.timeDay.floor(date) === +date;
4}This is more reliable than testing whether the time is 12:00 AM, as in some time zones midnight may not exist due to daylight saving.
# interval.round(date) · Source
Returns a new date representing the closest interval boundary date to date. For example, d3.timeDay.round(date) typically returns 12:00 AM local time on the given date if it is on or before noon, and 12:00 AM of the following day if it is after noon.
This method is idempotent: if the specified date is already rounded to the current interval, a new date with an identical time is returned.
# interval.ceil(date) · Source
Returns a new date representing the earliest interval boundary date after or equal to date. For example, d3.timeDay.ceil(date) typically returns 12:00 AM local time on the date following the given date.
This method is idempotent: if the specified date is already ceilinged to the current interval, a new date with an identical time is returned. Furthermore, the returned date is the maximum expressible value of the associated interval, such that interval.ceil(interval.ceil(date) + 1) returns the following interval boundary date.
# interval.offset(date[, step]) · Source
Returns a new date equal to date plus step intervals. If step is not specified it defaults to 1. If step is negative, then the returned date will be before the specified date; if step is zero, then a copy of the specified date is returned; if step is not an integer, it is floored. This method does not round the specified date to the interval. For example, if date is today at 5:34 PM, then d3.timeDay.offset(date, 1) returns 5:34 PM tomorrow (even if daylight saving changes!).
# interval.range(start, stop[, step]) · Source
Returns an array of dates representing every interval boundary after or equal to start (inclusive) and before stop (exclusive). If step is specified, then every stepth boundary will be returned; for example, for the d3.timeDay interval a step of 2 will return every other day. If step is not an integer, it is floored.
The first date in the returned array is the earliest boundary after or equal to start; subsequent dates are offset by step intervals and floored. Thus, two overlapping ranges may be consistent. For example, this range contains odd days:
1d3.timeDay.range(new Date(2015, 0, 1), new Date(2015, 0, 7), 2) // [2015-01-01T00:00, 2015-01-03T00:00, 2015-01-05T00:00]
While this contains even days:
1d3.timeDay.range(new Date(2015, 0, 2), new Date(2015, 0, 8), 2) // [2015-01-02T00:00, 2015-01-04T00:00, 2015-01-06T00:00]
To make ranges consistent when a step is specified, use interval.every instead.
# interval.filter(test) · Source
Returns a new interval that is a filtered subset of this interval using the specified test function. The test function is passed a date and should return true if and only if the specified date should be considered part of the interval. For example, to create an interval that returns the 1st, 11th, 21th and 31th (if it exists) of each month:
1d3.timeDay.filter(d => (d.getDate() - 1) % 10 === 0)
The returned filtered interval does not support interval.count. See also interval.every.
# interval.every(step) · Source
Returns a filtered view of this interval representing every stepth date. The meaning of step is dependent on this interval’s parent interval as defined by the field function. For example, d3.timeMinute.every(15) returns an interval representing every fifteen minutes, starting on the hour: :00, :15, :30, :45, etc. Note that for some intervals, the resulting dates may not be uniformly-spaced; d3.timeDay’s parent interval is d3.timeMonth, and thus the interval number resets at the start of each month. If step is not valid, returns null. If step is one, returns this interval.
This method can be used in conjunction with interval.range to ensure that two overlapping ranges are consistent. For example, this range contains odd days:
1d3.timeDay.every(2).range(new Date(2015, 0, 1), new Date(2015, 0, 7)) // [2015-01-01T00:00, 2015-01-03T00:00, 2015-01-05T00:00]
As does this one:
1d3.timeDay.every(2).range(new Date(2015, 0, 2), new Date(2015, 0, 8)) // [2015-01-03T00:00, 2015-01-05T00:00, 2015-01-07T00:00]
The returned filtered interval does not support interval.count. See also interval.filter.
# interval.count(start, end) · Source
Returns the number of interval boundaries after start (exclusive) and before or equal to end (inclusive). Note that this behavior is slightly different than interval.range because its purpose is to return the zero-based number of the specified end date relative to the specified start date. For example, to compute the current zero-based day-of-year number:
1d3.timeDay.count(d3.timeYear(now), now) // 177
Likewise, to compute the current zero-based week-of-year number for weeks that start on Sunday:
1d3.timeSunday.count(d3.timeYear(now), now) // 25
# d3.timeInterval(floor, offset[, count[, field]]) · Source
Constructs a new custom interval given the specified floor and offset functions and an optional count function.
The floor function takes a single date as an argument and rounds it down to the nearest interval boundary.
The offset function takes a date and an integer step as arguments and advances the specified date by the specified number of boundaries; the step may be positive, negative or zero.
The optional count function takes a start date and an end date, already floored to the current interval, and returns the number of boundaries between the start (exclusive) and end (inclusive). If a count function is not specified, the returned interval does not expose interval.count or interval.every methods. Note: due to an internal optimization, the specified count function must not invoke interval.count on other time intervals.
The optional field function takes a date, already floored to the current interval, and returns the field value of the specified date, corresponding to the number of boundaries between this date (exclusive) and the latest previous parent boundary. For example, for the d3.timeDay interval, this returns the number of days since the start of the month. If a field function is not specified, it defaults to counting the number of interval boundaries since the UNIX epoch of January 1, 1970 UTC. The field function defines the behavior of interval.every.
Intervals
The following intervals are provided:
# d3.timeMillisecond · Source
# d3.utcMillisecond
Milliseconds; the shortest available time unit.
# d3.timeSecond · Source
# d3.utcSecond
Seconds (e.g., 01:23:45.0000 AM); 1,000 milliseconds.
# d3.timeMinute · Source
# d3.utcMinute · Source
Minutes (e.g., 01:02:00 AM); 60 seconds. Note that ECMAScript ignores leap seconds.
# d3.timeHour · Source
# d3.utcHour · Source
Hours (e.g., 01:00 AM); 60 minutes. Note that advancing time by one hour in local time can return the same hour or skip an hour due to daylight saving.
# d3.timeDay · Source
# d3.utcDay · Source
# d3.unixDay · Source
Days (e.g., February 7, 2012 at 12:00 AM); typically 24 hours. Days in local time may range from 23 to 25 hours due to daylight saving. d3.unixDay is like d3.utcDay, except it counts days since the UNIX epoch (January 1, 1970) such that interval.every returns uniformly-spaced dates rather than varying based on day-of-month.
# d3.timeWeek · Source
# d3.utcWeek · Source
Alias for d3.timeSunday; 7 days and typically 168 hours. Weeks in local time may range from 167 to 169 hours due to daylight saving.
# d3.timeSunday · Source
# d3.utcSunday · Source
Sunday-based weeks (e.g., February 5, 2012 at 12:00 AM).
# d3.timeMonday · Source
# d3.utcMonday · Source
Monday-based weeks (e.g., February 6, 2012 at 12:00 AM).
# d3.timeTuesday · Source
# d3.utcTuesday · Source
Tuesday-based weeks (e.g., February 7, 2012 at 12:00 AM).
# d3.timeWednesday · Source
# d3.utcWednesday · Source
Wednesday-based weeks (e.g., February 8, 2012 at 12:00 AM).
# d3.timeThursday · Source
# d3.utcThursday · Source
Thursday-based weeks (e.g., February 9, 2012 at 12:00 AM).
# d3.timeFriday · Source
# d3.utcFriday · Source
Friday-based weeks (e.g., February 10, 2012 at 12:00 AM).
# d3.timeSaturday · Source
# d3.utcSaturday · Source
Saturday-based weeks (e.g., February 11, 2012 at 12:00 AM).
# d3.timeMonth · Source
# d3.utcMonth · Source
Months (e.g., February 1, 2012 at 12:00 AM); ranges from 28 to 31 days.
# d3.timeYear · Source
# d3.utcYear · Source
Years (e.g., January 1, 2012 at 12:00 AM); ranges from 365 to 366 days.
Ranges
For convenience, aliases for interval.range are also provided as plural forms of the corresponding interval.
# d3.timeMilliseconds(start, stop[, step]) · Source
# d3.utcMilliseconds(start, stop[, step])
Aliases for d3.timeMillisecond.range and d3.utcMillisecond.range.
# d3.timeSeconds(start, stop[, step]) · Source
# d3.utcSeconds(start, stop[, step])
Aliases for d3.timeSecond.range and d3.utcSecond.range.
# d3.timeMinutes(start, stop[, step]) · Source
# d3.utcMinutes(start, stop[, step]) · Source
Aliases for d3.timeMinute.range and d3.utcMinute.range.
# d3.timeHours(start, stop[, step]) · Source
# d3.utcHours(start, stop[, step]) · Source
Aliases for d3.timeHour.range and d3.utcHour.range.
# d3.timeDays(start, stop[, step]) · Source
# d3.utcDays(start, stop[, step]) · Source
# d3.unixDays(start, stop[, step]) · Source
Aliases for d3.timeDay.range, d3.utcDay.range, and d3.unixDay.range.
# d3.timeWeeks(start, stop[, step])
# d3.utcWeeks(start, stop[, step])
Aliases for d3.timeWeek.range and d3.utcWeek.range.
# d3.timeSundays(start, stop[, step]) · Source
# d3.utcSundays(start, stop[, step]) · Source
Aliases for d3.timeSunday.range and d3.utcSunday.range.
# d3.timeMondays(start, stop[, step]) · Source
# d3.utcMondays(start, stop[, step]) · Source
Aliases for d3.timeMonday.range and d3.utcMonday.range.
# d3.timeTuesdays(start, stop[, step]) · Source
# d3.utcTuesdays(start, stop[, step]) · Source
Aliases for d3.timeTuesday.range and d3.utcTuesday.range.
# d3.timeWednesdays(start, stop[, step]) · Source
# d3.utcWednesdays(start, stop[, step]) · Source
Aliases for d3.timeWednesday.range and d3.utcWednesday.range.
# d3.timeThursdays(start, stop[, step]) · Source
# d3.utcThursdays(start, stop[, step]) · Source
Aliases for d3.timeThursday.range and d3.utcThursday.range.
# d3.timeFridays(start, stop[, step]) · Source
# d3.utcFridays(start, stop[, step]) · Source
Aliases for d3.timeFriday.range and d3.utcFriday.range.
# d3.timeSaturdays(start, stop[, step]) · Source
# d3.utcSaturdays(start, stop[, step]) · Source
Aliases for d3.timeSaturday.range and d3.utcSaturday.range.
# d3.timeMonths(start, stop[, step]) · Source
# d3.utcMonths(start, stop[, step]) · Source
Aliases for d3.timeMonth.range and d3.utcMonth.range.
# d3.timeYears(start, stop[, step]) · Source
# d3.utcYears(start, stop[, step]) · Source
Aliases for d3.timeYear.range and d3.utcYear.range.
Ticks
# d3.timeTicks(start, stop, count) · Source
Equivalent to d3.utcTicks, but in local time.
# d3.timeTickInterval(start, stop, count) · Source
Returns the time interval that would be used by d3.timeTicks given the same arguments.
# d3.utcTicks(start, stop, count) · Source
Returns an array of approximately count dates at regular intervals between start and stop (inclusive). If stop is before start, dates are returned in reverse chronological order; otherwise dates are returned in chronological order. The following UTC time intervals are considered:
- 1 second
- 5 seconds
- 15 seconds
- 30 seconds
- 1 minute
- 5 minutes
- 15 minutes
- 30 minutes
- 1 hour
- 3 hours
- 6 hours
- 12 hours
- 1 day
- 2 days
- 1 week
- 1 month
- 3 months
- 1 year
Multiples of milliseconds (for small ranges) and years (for large ranges) are also considered, following the rules of d3.ticks. The interval producing the number of dates that is closest to count is used. For example:
1start = new Date(Date.UTC(1970, 2, 1)) 2stop = new Date(Date.UTC(1996, 2, 19)) 3count = 4 4d3.utcTicks(start, stop, count) // [1975-01-01, 1980-01-01, 1985-01-01, 1990-01-01, 1995-01-01]
If count is a time interval, this function behaves similarly to interval.range except that both start and stop are inclusive and it may return dates in reverse chronological order if stop is before start.
# d3.utcTickInterval(start, stop, count) · Source
Returns the time interval that would be used by d3.utcTicks given the same arguments. If there is no associated interval, such as when start or stop is invalid, returns null.
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: ISC License: LICENSE:0
Reason
2 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
- Warn: Project is vulnerable to: GHSA-gcx4-mw62-g8wm
Reason
Found 9/28 approved changesets -- score normalized to 3
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/d3/d3-time/publish.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish.yml:16: update your workflow using https://app.stepsecurity.io/secureworkflow/d3/d3-time/publish.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:13: update your workflow using https://app.stepsecurity.io/secureworkflow/d3/d3-time/test.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:14: update your workflow using https://app.stepsecurity.io/secureworkflow/d3/d3-time/test.yml/main?enable=pin
- Info: 0 out of 4 GitHub-owned GitHubAction dependencies pinned
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Info: jobLevel 'contents' permission set to 'read': .github/workflows/publish.yml:12
- Warn: no topLevel permission defined: .github/workflows/publish.yml:1
- Warn: no topLevel permission defined: .github/workflows/test.yml:1
- Info: no jobLevel write permissions found
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
Project has not signed or included provenance with any releases.
Details
- Warn: release artifact v2.1.1 not signed: https://api.github.com/repos/d3/d3-time/releases/41213785
- Warn: release artifact v2.1.0 not signed: https://api.github.com/repos/d3/d3-time/releases/41213580
- Warn: release artifact v2.0.0 not signed: https://api.github.com/repos/d3/d3-time/releases/28975113
- Warn: release artifact v2.1.1 does not have provenance: https://api.github.com/repos/d3/d3-time/releases/41213785
- Warn: release artifact v2.1.0 does not have provenance: https://api.github.com/repos/d3/d3-time/releases/41213580
- Warn: release artifact v2.0.0 does not have provenance: https://api.github.com/repos/d3/d3-time/releases/28975113
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 13 are checked with a SAST tool
Score
3.5
/10
Last Scanned on 2025-01-27
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More