
Security News
npm Adopts OIDC for Trusted Publishing in CI/CD Workflows
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
js-joda-timezone
Advanced tools
Implementation of the js-joda ZoneRulesProvider, providing the bindings to the iana tzdb, using latest zone file generated by moment-timezone
Install joda using npm
npm install js-joda
npm install js-joda-timezone
var jsJoda = require('js-joda')
require('js-joda-timezone')
var { LocalDateTime, ZoneId, ZonedDateTime } = jsJoda;
LocalDateTime
.parse('2016-06-30T11:30')
.atZone(ZoneId.of('Europe/Berlin'))
.toString() // 2016-06-30T11:30+02:00[Europe/Berlin]
ZonedDateTime
.parse('2016-06-30T11:30+02:00[Europe/Berlin]')
.withZoneSameInstant(ZoneId.of('America/New_York'))
.toString() // 2016-06-30T05:30-04:00[America/New_York]
ZonedDateTime
.parse('2016-06-30T11:30+02:00[Europe/Berlin]')
.withZoneSameLocal(ZoneId.of('America/New_York'))
.toString() // 2016-06-30T11:30-04:00[America/New_York]
import { ZonedDateTime, ZoneId } from 'js-joda'
import 'js-joda-timezone'
const zdt = ZonedDateTime.now(ZoneId.of('America/New_York'))
<script src="../dist/js-joda.js"></script>
<script src="../dist/js-joda-timezone.js"></script>
<script>
// copy all js-joda classes to the global scope
for(let key in JSJoda) { this[key] = JSJoda[key]; }
LocalDateTime
.parse('2016-06-30T11:30')
.atZone(ZoneId.of('Europe/Berlin'))
.toString() // 2016-06-30T11:30+02:00[Europe/Berlin]
ZonedDateTime
.parse('2016-06-30T11:30+02:00[Europe/Berlin]')
.withZoneSameInstant(ZoneId.of('America/New_York'))
.toString() // 2016-06-30T05:30-04:00[America/New_York]
ZonedDateTime
.parse('2016-06-30T11:30+02:00[Europe/Berlin]')
.withZoneSameLocal(ZoneId.of('America/New_York'))
.toString() // 2016-06-30T11:30-04:00[America/New_York]
</script>
If you don't need all the historical data that js-joda-timezone provides, you can instead use one of the reduced files ize builds:
js-joda-timezone-10-year-range.js
covers +- five years from the current version's releasejs-joda-timezone-1970-2030.js
covers from 1970 to 2030js-joda-timezone-2012-2022.js
covers from 2012 to 2022To use one of these, just change your import path to the following format:
import 'js-joda-timezone/dist/js-joda-timezone-1970-2030'
js-joda-timezone is released under the BSD 3-clause license:
The author of joda time and the lead architect of the JSR-310 is Stephen Colebourne.
The json versions of the iana tzdb are imported from and generated with moment-timezone.
2.1.1
FAQs
iana tzdb timezone bindings for js-joda
The npm package js-joda-timezone receives a total of 1,211 weekly downloads. As such, js-joda-timezone popularity was classified as popular.
We found that js-joda-timezone demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
Research
/Security News
A RubyGems malware campaign used 60 malicious packages posing as automation tools to steal credentials from social media and marketing tool users.
Security News
The CNA Scorecard ranks CVE issuers by data completeness, revealing major gaps in patch info and software identifiers across thousands of vulnerabilities.