CyberAlien @cyberalien_dev

@balazsorban44 @pnpmjs There is even shorter option: try @antfu/ni package Then you can type "ni" to install, "nr" to run regardless of what package manager code is using. Short and easy to use.

CSS just killed another dark-mode snippet. 🔥 `light-dark()` for images is Baseline, newly available since September 2026. Colors already were; Safari 27 closed the gap for images and gradients. Before this, a dark hero image meant a second rule inside a media query. Now ⤵️ one declaration. 😎

StackBlitz/Bolt has been supporting my work, with no strings attached. 🙏 More than thanking them, I want to point out a fact: without their support for my full-time work on Volar, we could never have shipped Volar v3. That work fed into what became TS 7.1 Content Mappers, and helped improve the developer experience across the frontend ecosystem in a deeper way. I've been a bit quiet lately, but I haven't been resting. I might have something interesting to show you soon. 🤞

mohammad @asleMammadam

2 weeks ago

volar is the language tooling behind the official vue editor extension and vue-tsc. we sponsor @johnsoncodehk at $1,000/month.

1 0 18 6K 1

@asleMammadam Thank you very very much for supporting open source work! Such support is very much needed to maintain many open source projects, including mine. Thank you!

Browsers should do CSS layout off the main thread! 🤓 Top left: @ladybirdbrowser (work in progress) Others: Chrome, Safari, Firefox

I am losing roughly $800 a month by working on MSW full-time while it's one of the most used projects in the ecosystem. Please, if MSW provides you any value, consider becoming a sponsor. I mean it when I say every contribution counts. Thank you ❤️ github.com/sponsors/mswjs

This is a real problem for maintainers. AI “Security Researchers” making up scenarios out of literally any bug or even possible user mistake, as vulnerabilities. We should not let it become normal. Otherwise real vulnerabilities won’t be taken seriously!

Matteo Collina @matteocollina

3 weeks ago

Last night I received "5" potential vulnerabilities. How many were actual vulnerabilities? 0. How many were bugs? 5. How many were from the same slop-bot? 5. The worst part is that if you don't engage with the AI slop horde, they will escalate, and you get a CVE slapped on

11 6 119 22K 10

@ItsLeeDB @dannypostma Good news. According to some posts I've seen, beta is very buggy on Apple silicone and people are very frustrated. Though could be edge cases.

@semihdotcom @figma @sketch Same. Both are good. Figma is better for working with vectors (designing icons). Sketch is better for working with raster images.

New location for pre-rendered icon components: gitlab.com/iconify-icons Packages for React, Vue, Svelte and SolidJS. One branch per icon set, which includes all icons in that icon set. Automatically kept up to date. Main branch lists all icon sets. Usage instructions in readme files. Current stats: 222 icon sets, 367704 icons. Components are rendered as SVG+CSS, where .css files include all attributes and SVG includes only tags with class names. This massively reduces HTML size by moving majority of code to CSS.

PSA: if you have a @voidzerodev sponsorship on GitHub and saw it cancelled - don't worry. We are in the process of switching our billing method and will re-activate them soon.

@maxleiter Resist the temptation! As a former very active WoW player, I fully understand. It is very addictive. It used to be the best game ever. Let old memories remain memories. Don't ruin them by playing again, you will only be eventually disappointed.

See readme for long version. Basically, NPM stores full package.json contents for all versions in one huge metadata. That includes "exports" field, which is useless, yet it stores it. For large icon sets, which have large "exports" field, after publishing too many versions (published over a year or so), metadata became too big, hitting 100mb limit on NPM, so new versions cannot be published anymore. To make it worse, NPM does not allow unpublishing old versions, so I can't free up space. Can't publish new versions, can't unpublish old versions. All because for some reason NPM stores an entire package.json of every single published version in one single metadata file and includes everything in it, including "exports" field.

Due to NPM issues, icon components for Vue, Svelte, React and SolidJS have been migrated from NPM to GitHub. From now on, you can install components from branches of repositories: github.com/iconify/icons-… Readme has long explanation. NPM packages will eventually be deprecated. For other frameworks: React components: github.com/iconify/icons-… Svelte components: github.com/iconify/icons-… SolidJS components: github.com/iconify/icons-…

Currently attempting publishing icon components again. NPM: fails for large icon sets. GitHub: branches disappearing. Attempt 3: moving to GitLab. If successful, icon components will have a new home here: gitlab.com/iconify-icons

After debugging, I've noticed that it is the same branches disappearing in all 4 repositories. All those branches are for icon sets that have many icons, thus many files: over 10k files. I don't see such limit anywhere in docs and what's worse is branches disappearing without error.

Earlier today I've announced migration of icon packages from NPM to GitHub. Well... that failed. Branches on GitHub started randomly disappearing. GitHub supposed to have limit of 5k branches per repo, but cannot handle mere 200 branches. Did not expect that. Need to rethink it...

@saku_shiina How so? All packages are kept up to date, they just changed location.

Iconify has generated components for each icon set for Vue, Svelte, React and Solid, such as "@iconify-vue/mdi". That's almost 1k packages! Due to NPM registry issues I'm currently moving them to GitHub. NPM client can install from GitHub, so NPM registry can be avoided. I'll write a long post about this later when migration complete. After migration, those ~1k packages can be installed from GitHub (replace framework and icon set prefix): npm install github:iconify/icons-vue#mdi