Topic
When the original storage index was designed, jsDelivr tracked roughly 350,000 unique files. By the time we replaced it, that number had grown to more than 600 million. We moved the index from Redis to MariaDB, migrated storage from Amazon S3 to Wasabi, compressed and cleaned up the stored data, and reduced the GitHub API work needed for uncached
Over the past few months, we upgraded the /+esm toolchain, worked through the open compatibility reports, and then used production APM data to find the failures that had not been reported yet. This post covers what we found and the changes now running in production. When we introduced jsDelivr’s ESM bundling service, the idea was simple: take a package
It's been a while since our last update, but don't worry - we've been hard at work! Check out the summary of updates we're launching! ESM - ES Modules Support Since launching the support for ESM about two years ago, we've been working on improving the compatibility with the existing packages, as
A long time has passed since the last update. Since then jsDelivr has improved and grown a lot. New backend! * A completely automated system that works by proxying npm and Github directly. All a user needs to do is publish his package to the npm registry and it will instanly appear on the jsDelivr CDN * To protect our users all
Introducing libgrabber! I am happy to announce that jsDelivr is now in process of becoming fully automated. libgrabber is an app that runs on our servers and can keep projects hosted at jsDelivr updated automatically without requiring the author or any contributors to manually process and upload the new versions. This is very important as the repo is quite heavy
