js-joda
import-maps
js-joda | import-maps | |
---|---|---|
7 | 45 | |
1,587 | 2,636 | |
0.7% | 1.1% | |
7.9 | 3.1 | |
9 days ago | 6 months ago | |
JavaScript | JavaScript | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
js-joda
-
Everything you need to know about Date in Programming
js-joda
-
Making your datepicker easier to work with
So first, a simple example of how this works. Using our "What is your birthday" example, we can mock up this code. Note: I'm using TypeScript because it enforces the concepts at compile time, but the JsJoda library itself enforces the concepts at runtime so that we get the best of both.
-
[HELP] Time elapsed since midnight breaks on days when DST changes
Dealing with human dates is non-trivial thanks to localization. The easiest thing to do is to start with something zone agnostic (like UTC or epoch) do your date calculation, and then shift that into the locale you want. date-fns is fine for basic date math, but if you want something more robust, with a more cohesive API, I'd recommend js-joda.
-
You don't (may not) need Moment.js
How come the js-joda library is never mentioned in discussions about javascript date/time libraries? its API is perfect and it has been around forever. but instead the community seems to keep inventing more and more new datetime libraries. i don't understand why js-joda seems to be ignored
https://js-joda.github.io/js-joda/
- Temporal: Getting started with JavaScript's new date time API
-
Updates from the 81st meeting of TC39
I've been getting by with js joda. Temporal is a welcome addition.
-
How to format dates without Moment.js
Support for the domain models LocalDate, LocalDateTime, ZonedDateTime, Instant, Duration and Period. Also, supports IANA timezone, adding the plugin @js-joda/timezone you'll have access to the IANA timezone database with all the timezones available.
import-maps
-
It is hard to avoid JavaScript
Long time huge fan of JS. I appreciate your calling out the multi-paradigm aspect; having these first class functions & prototype based inheritance has been so flexible.
TC39 has done a great job shaping the language over the years. New capabilities are usually well thought out & integrate well. Async await has been amazing.
The one major miss that makes me so sad and frustrated is modules; js has gotten better everywhere except it's near requirement for build tooling. Being able to throw some scripts on a page and go is still an unparalleled experience in the world, is so direct & tactile an experience. EcmaScript Modules was supposed to improve things, help get us back, but imports using url specifiers made the whole thing non-modular, was a miss. We're still tangled & torn. Import-maps has finally fixed but it's no where near as straightforward, and it still doesn't work in workers, which leaves us infuriatingly shirt of where the past was. https://github.com/WICG/import-maps/issues/2
-
'Mother of all breaches' data leak reveals 26B account stolen records
makes sure your app is getting the download it expects. Adoption is probably pretty minimal though. https://developer.mozilla.org/en-US/docs/Web/Security/Subres...
I think the big thing making this unlikely though is that very few folks use cdns these days. We designed ESM as a module system for the language, but then took a good fraction of a decade to build import-maps, to let us actually use modules in a modular way. Good news, we can finally use modules modularly! https://caniuse.com/import-maps
Bad news? Oh import-maps only works for the simplest case. Doesn't work in webworkers/service workers. https://github.com/WICG/import-maps/issues/2
The point is that single page apps almost always are bundled together, as using CDNs hasn't even been technically possible.
Also, CDNs are kind of somewhat pointless, now that http caches are partitioned by origin (for security reasons). They might have better anycast infrastructure to get the content out faster, but without the caching there's no inherent advantage. The user will download the same jquery file again in each site they go to, no already having it cached anymore. Bah humbug!
- Rails Frontend Bundling - Which one should I choose?
- ESM dynamic imports
-
JavaScript import maps are now supported cross-browser
https://github.com/WICG/import-maps/issues/2
-
We Added Package.json Support to Deno
Bare specifiers has been the tragedy of ESM. Nice module syntax... that is utterly u deoyable & which has had to have awful de-modularizing specifiers hard-coded into each file to make it work. Abominable sin to introduce "modules" to JS/es2015 then spend a decade dragging everyone along with no story for how to have modular modules.
Import-maps are like "here" to fix this on the web... finally... except they only are shipping to the happiest sunniest easiest case, with Web Workers being totally shit out of luck in spite of some very simple straightforward suggested paths forward. https://github.com/WICG/import-maps/issues/2
I think Deno is making pretty good tradeoffs along the way here. This looks like package.json at surface level, but there is a nightmare of complexity under the surface. Typescript, ESM, cjs all have various pressures they create & in Node it's just incredibly tight & tense dealing with packaging, where-as Deno's happy path of Typescript first does not slowly tatters one over time. It really has been super pleasant being free of the previous world, and having something much more web-platform centric, more intented, with less assembly & less building, and more doing the actual coding.
I really hope import-maps eventually get broader support. Maybe this long-dwelling webworker issue should be brought up with WinterCG.
-
Import maps 101
Import maps proposal
-
You Might Not Need Module Federation: Orchestrate your Microfrontends at Runtime with Import Maps
The concept of Import Maps was born in 2018 and made its long way until it was declared a new web standard implemented by Chrome in 2021 and some other browsers.
-
Getting an "import file" syntax right for ArkScript
For package managers, you can use something like import maps to let the user specify which path points to what package, and resolve it properly.
-
Deno 1.28: Featuring 1.3M New Modules
Huh. I was about to complain that this breaks with web standards, but apparently it's being proposed as a standard feature: https://github.com/WICG/import-maps
Interesting!
What are some alternatives?
Luxon - ⏱ A library for working with dates and times in JS
esbuild - An extremely fast bundler for the web
date-fns - ⏳ Modern JavaScript date utility library ⌛️
es-module-shims - Shims for new ES modules features on top of the basic modules support in browsers
dayjs - ⏰ Day.js 2kB immutable date-time library alternative to Moment.js with the same modern API
importmap-rails - Use ESM with importmap to manage modern JavaScript in Rails without transpiling or bundling.
moment - Parse, validate, manipulate, and display dates in javascript.
esm.sh - A fast, smart, & global CDN for modern(es2015+) web development.
proposal-temporal - Provides standard objects and functions for working with dates and times.
single-spa - The router for easy microfrontends
You-Dont-Need-Momentjs - List of functions which you can use to replace moment.js + ESLint Plugin
deno - A modern runtime for JavaScript and TypeScript.