This is a very cool little addition to UNPKG.
Just include https://t.co/jSiQR0uVVw, and it'll automatically run TypeScript (and JSX!) blocks it finds in the page!
Props to https://t.co/rAhWezioZE for the inspiration ๐
Also new: https://t.co/I2r5X6EDwR โจ
Write TypeScript + JSX straight in your HTML with no build step, bundler, or import map. Bare imports just work, compiled on the fly by https://t.co/Tzr1wpPgXq.
Great for demos!
Introducing https://t.co/Tzr1wpPgXq ๐
Any npm package as browser-ready ES modules.
โข TypeScript + JSX
โข imports resolve to UNPKG
โข zero build step
Props to https://t.co/lL0VGcvJfC for pioneering npm bundling in the cloud. You can now do this on UNPKG too!
๐ข announcing vite-plugin-unpkg
vite-plugin-unpkg is a @vite_js plugin that maps @unpkg links to local packages in your monorepo.
This lets you use the no-build ethos of unpkg using direct links to unpkg even before your packages are published.
~~attention cf'ers~~
[email protected] dropped
admindo .dev is now live. enjoy the nonfunctional skeleton!
AdminDO, the web and CLI admin for @cloudflare Durable Objects
what's cool about this project:
* no-build frontend via @unpkg
* make your own admindo plugins
* rally the community around a single architecture
what do you want to see next?
<script type=โimportmapโ> is underrated
This is the only way I ever want to load dependencies in the browser. Straight from @unpkg.
Bundling and deploying all that stuff myself over and over again is so tired.
I relaunched @unpkg a few weeks ago, completely rewritten from scratch!
The backend is:
- @cloudflare Workers
- @flydotio and @bunjavascript for serving files
- esbuild
The frontend:
- @preactjs for components + hydration
- @tailwindcss
Source:
https://t.co/6zpaaZDfN2
@levelsio Our apologies for the downtime! We transitioned to a new backend architecture this morning that should resolve any issues you were seeing. The site has been completely rebuilt on top of Cloudflare Workers and should now be fast and responsive.
UNPKG now serves all traffic over HTTP/3! ๐ฅ
With @Cloudflare, it's as easy as toggling a checkbox. We will be anxious to see how much of our traffic takes advantage of HTTP/3 over the coming months!
@nwoolls We deployed support for package.exports this week, and it turns out we had an issue with deep imports in packages that specify package.exports. This should be fixed now, and the URL you gave us now works for us. Apologies for the inconvenience.
@JeremyL93881162@nwoolls We deployed support for package.exports this week, and it turns out we had a bug. The URL you linked us to should work now. Apologies for the inconvenience.
@ChrisGannon@greensock It appears that @greensock was using https://t.co/SeT8CbXZ46 (unsupported) instead of https://t.co/vseEVT2D4Q for some files. We are redirecting all https://t.co/SeT8CbXZ46 traffic to the .com now, so your projects should work again. Apologies for the inconvenience.