There’s a link with one source in the replies too but it does seem possible that it’s due to their Azure migration
bsky.app/profile/mosh...
There’s a link with one source in the replies too but it does seem possible that it’s due to their Azure migration
bsky.app/profile/mosh...
Thank! It’s been going for a *while* , eh? We moved from Azure Pipelines back when GitHub wasn’t Microsoft and it seems like we are going right back 😅
Oh I missed that. It was exactly what I had planned for Stacks, even had the lexicon mapped up for bookmarks.
I’m gonna take a peak later today, what status of that PR is
💪
It does add confusion that npm is a package manager while npx is a package runner, so that makes npmx.. a package manager runner? 🤭
I saw someone somewhere mention that it might have to do with some grand migration to Azure but I never verified it. The amount of slowdown / downtime this past year's been substantial - that's for sure.
I remember my ecosystem intro months (weirdly) fondly and most of what I’ve learned at the time was quite boring, battle tested. I wonder how it is these days, with AI, thoughtful and shiny solutions.. I felt overwhelmed at the time; is today’s landscape easier or harder to navigate?
Do you get taken aback by an influx of otherwise dull LinkedIn posts talking about this new thing. Do workspaces update their onboarding docs with it as the starting point? Does your mentor introduce you to it as your first packages browser?
When something like npmx.dev that genuinely touches and potentially drastically changes so many areas of a developer’s life, I always wonder how much the ripples of celebration touch the day to day lives of “blue collar workers”, devs and execs outside of the community.
The year of atproto in mainstream came before the year of Linux on desktop, eh? 🤭
npmx.dev is a much needed breath of fresh air in the packages registry space, baked by a battle tested set of maintainers and an incredibly passionate community along side of atproto builders. If you like to bet on alpha software from time to time - npmx has all the green flags you need 😉
Well the thing is, there’s already a simple “toggle all AI off” option. So if AI was the main reason behind that clause, wouldn’t they just ship an “underaged” version with AI disabled by default? I’m not sure I fully get this development.
Woah, this is sick, congratulations!
Real talk tho: been installing micro-editor.github.io on my VMs ever since I found it
npmx is currently lacking custom badges which I tried to patch up with this PR. With it, you should be able to migrate pretty easily
github.com/npmx-dev/npm...
See these examples
github.com/npmx-dev/npm...
I think Mary’s been leading the bundle impact analysis efforts
github.com/npmx-dev/npm...
I’ve also reconsidered what the @atplay.blue client actually needs in terms of interactivity, and a static frontend should do the job for quite a while, especially with modern HTML features like view transitions.
SolidStart v2 bun compatibility is in a weird limbo - it only works about half the time, and Solid v2 still isn’t fully compatible with SolidStart v2.
..and also on JSR because I've never had the incentive to explore the platform before.
jsr.io/@moshyfawn/t...
Welp, I’ve circled back to ElysiaJS - there’s still nothing else that integrates as fully with Bun. I ended up fixing my main issue with Tailwind and Kita by dissecting both their processes and writing a plugin that ties together runtime templates with Tailwind’s parser.
What in the ICQ? 🤪
What if.. someone saved the post instead? 😈
There's also Gunshi which I keep seeing but haven't had a chance to try
github.com/kazupon/gunshi
bomb.sh is a nice simple yet quite robust solution with packages for args parsing and even autocomplete since not too long ago.