time-elements

v3.0.0

Formats a timestamp as a localized string or as relative text that auto-updates in the user's browser. For more information about how to use this package see README

Latest version published 5 years ago

License: MIT

NPM

GitHub

Package Health Score

56 / 100

security
No known security issues
popularity
Small
maintenance
Inactive
community
Active

Security

No known security issues

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions

Version				Vulnerabilities	License Risk
3.0.0	\|	06/2019		0 C 0 H 0 M 0 L	0 H 0 M 0 L
2.0.2	\|	05/2019	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.2.0	\|	07/2018		0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.6.1	\|	07/2016		0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

MIT

Security Policy

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Small

Weekly Downloads (144)

GitHub Stars: 3.53K
Forks: 171
Contributors: 50

Direct Usage Popularity

The npm package time-elements receives a total of 144 downloads a week. As such, we scored time-elements popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package time-elements, we found that it has been starred 3,528 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Active

Readme.md: Yes
Contributing.md: Yes
Code of Conduct: Yes
Contributors: 50
Funding: No

With more than 10 contributors for the time-elements repository, this is possibly a sign for a growing and inviting community.

Embed Package Health Score Badge

Maintenance

Inactive

deprecated

Commit Frequency

Open Issues: 10
Open PR: 4
Last Release: 5 years ago
Last Commit: 3 months ago

Further analysis of the maintenance status of time-elements based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

An important project maintenance signal to consider for time-elements is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: not defined

Age: 8 years
Dependencies: 0 Direct
Versions: 15
Install Size: 57.4 kB
Dist-tags: 2
# of Files: 14
Maintainers: 19
TS Typings: No

time-elements has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.

Readme

<time> element extensions

Formats a timestamp as a localized string or as relative text that auto-updates in the user's browser.

This allows the server to cache HTML fragments containing dates and lets the browser choose how to localize the displayed time according to the user's preferences. For example, the server may have cached the following generated markup:


  April 1, 2014 4:30pm

Every visitor is served the same markup from the server's cache. When it reaches the browser, the custom local-time JavaScript localizes the element's text into the local timezone and formatting.


  1 Apr 2014 21:30

Dates are displayed before months, and a 24-hour clock is used, according to the user's browser settings.

If the browser's JavaScript is disabled, the default text served in the cached markup is still displayed.

Installation

Available on npm as time-elements.

$ npm install time-elements

Usage

This component provides three custom subtypes of the standard HTML <time> element. All custom time elements MUST have a datetime attribute set to an ISO 8601 formatted timestamp.

relative-time

A relative time-ago-in-words description can be generated by using the relative-time element extension.

Add a `` element to your markup. Provide a default formatted date as the element's text content (e.g. April 1, 2014).


  April 1, 2014

Depending on how far in the future this is being viewed, the element's text will be replaced with one of the following formats:

6 years from now
20 days from now
4 hours from now
7 minutes from now
just now
30 seconds ago
a minute ago
30 minutes ago
an hour ago
20 hours ago
a day ago
20 days ago
on Apr 1, 2014

So, a relative date phrase is used for up to a month and then the actual date is shown.

time-until

You can use time-until to always display a relative date that's in the future. It operates much like ``, except in the reverse, with past events shown as just now and future events always showing as relative:

10 years from now
20 days from now
6 hours from now
20 minutes from now
30 seconds from now
just now

Add a `` element to your markup. Provide a default formatted date as the element's text content (e.g. April 1, 2024).


  April 1, 2024

time-ago

An always relative time-ago-in-words description can be generated by using the time-ago element extension. This is similar to the relative-time extension. However, this will never switch to displaying the date. It strictly shows relative date phrases, even after a month has passed.


  April 1, 2014

For example, if this markup is viewed two years in the future, the element's text will read 2 years ago.

Micro format

The optional format="micro" attribute shortens the descriptions to 1m, 1h, 1d, 1y.


  April 1, 2014

local-time

This custom time extension is useful for formatting a date and time in the user's preferred locale format.


  April 1, 2014 4:30PM PDT

When this markup is viewed in a CDT timezone, it will show Apr 1, 2014 6:30PM. If it's viewed in a browser with European date preferences, it will read 1 Apr 2014 18:30.

Options

Attribute	Options	Description
`datetime`	ISO 8601 date	Required date of element `2014-06-01T13:05:07Z`
`year`	2-digit, numeric	Format year as `14` or `2014`
`month`	short, long	Format month as `Jun` or `June`
`day`	2-digit, numeric	Format day as `01` or `1`
`weekday`	short, long	Format weekday as `Sun` or `Sunday`
`hour`	2-digit, numeric	Format hour as `01` or `1`
`minute`	2-digit, numeric	Format minute as `05` or `5`
`second`	2-digit, numeric	Format second as `07` or `7`
`time-zone-name`	short, long	Display time zone as `GMT+1` or by its full name

Browser Support

Browsers without native custom element support require a polyfill.

Chrome
Firefox
Safari
Microsoft Edge

time-elements development dependencies

chai karma mocha eslint rollup flow-bin karma-chai @babel/core karma-mocha webcomponents.js babel-preset-github rollup-plugin-babel eslint-plugin-github karma-mocha-reporter karma-chrome-launcher

FAQs

What is time-elements?

Formats a timestamp as a localized string or as relative text that auto-updates in the user's browser. Visit Snyk Advisor to see a full health score report for time-elements, including popularity, security, maintenance & community analysis.

Is time-elements popular?

The npm package time-elements receives a total of 144 weekly downloads. As such, time-elements popularity was classified as small. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is time-elements well maintained?

We found indications that time-elements is an Inactive project. See the full package health analysis to learn more about the package maintenance status.

Is time-elements safe to use?

The npm package time-elements was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 7 November-2024, at 12:35 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP