import-maps
dayjs
import-maps | dayjs | |
---|---|---|
45 | 98 | |
2,629 | 45,796 | |
0.8% | - | |
3.1 | 6.9 | |
5 months ago | 3 days ago | |
JavaScript | JavaScript | |
GNU General Public License v3.0 or later | MIT License |
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.
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!
dayjs
-
Mastering Time: State-of-the-Art Date Handling in JavaScript
Similar API to Moment.js: Day.js provides a familiar API, making it easier for developers previously using Moment.js to transition.
-
The Day.js Dilemma: How Should We Handle OSS Maintainers Going MIA?
As web developers, we heavily rely OSS packages. One popular example is Day.js, a JS lib for parsing, validating, manipulating, and formatting dates. It's a widely-used alternative to Moment, with over 17mil weekly downloads on npm.
A critical bug was discovered in Day.js (see: https://github.com/iamkun/dayjs/pull/2118) causing incorrect date manipulation (add, subtract) when in UTC TZ. This could have severe implications for any project relying on Day.js for date-related functionality. However, the maintainer of the project appears to be unresponsive, leaving the bug unresolved and the future of the library uncertain.
This raises some important questions for our community:
- At what point should we consider a widely-used OSS project "abandoned" if the maintainer is unresponsive?
- Is forking the project the best solution, or should we first try to reach out to the maintainer through other channels?
- Are there established community guidelines around responsiveness expectations for widely-used OSS projects?
- What are successful examples of community-driven forks or maintenance after a maintainer stepped away?
I am very aware that many of these developers give their spare time for free for these projects, with little or no payment, and I am very thankful for all their work. This developer does get some money (a small amount?) through OpenCollective, and possibly also works for a company (in China?) that makes a UI library, which I think uses Day.js internally.
-
JavaScript Libraries That You Should Know
11. DayJs
-
Best date library to handle timezones in React Native?
DayJS has issues with its timezone plugin not compatible with Hermes engine https://github.com/iamkun/dayjs/issues/1942
-
Everything you need to know about Date in Programming
Date.js
-
Complete Tutorial: React Admin Panel with refine and daisyUI
We have to install refine's support packages for React Table and React Hook Form. We are using Tailwind Heroicons for our icons, the Day.js library for time calculations and Recharts library to plot our charts for KPI data. So, run the following and we are good to go:
-
Managify: Manage Your Teams Easily
DayJS is a lightweight and fast JavaScript library for manipulating dates and times. It offers a moment.js-like API but with a much smaller footprint.
- is there a date calculate script/libary ?
-
What library do you use to handle dates?
I use Day.js in my projects.
-
Flash News App React Native (Expo^)
well, I haven't reviewed the code, I just checked package.json and I'll suggest you to ditch moment.js Even the creator recommends ditching it. dayjs is a fantastic alternative.
What are some alternatives?
esbuild - An extremely fast bundler for the web
Luxon - ⏱ A library for working with dates and times in JS
es-module-shims - Shims for new ES modules features on top of the basic modules support in browsers
date-fns - ⏳ Modern JavaScript date utility library ⌛️
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.
moment-timezone - Timezone support for moment.js
single-spa - The router for easy microfrontends
countdown.js - Super simple countdowns.
deno - A modern runtime for JavaScript and TypeScript.
proposal-temporal - Provides standard objects and functions for working with dates and times.