antfu.me
A ship in harbor is safe, but that is not what ships are built for.
creator → @sli.dev • @unocss.dev • @vueuse.org • @vitest.dev • elk.zone
core team → @nuxt.com • @vite.dev • vuejs.org
maintainer → @shiki.style • eslint.style
he/him → antfu.me
307 posts
11,736 followers
837 following
Regular Contributor
Active Commenter
comment in response to
post
Well. When you are already in a thread you can’t create a sub thread. This is even sillier 😇
comment in response to
post
My question as well. Only sometime you have to use it for some organizations.
comment in response to
post
Good idea, would your browser support CJS as well?
comment in response to
post
deps and devDeps are confusing to a lot of people already, I didn’t want to introduce too many concepts at once as peer and optional mostly matter only to library authors where they should already familiar with those
package.yank is something new to me, thanks for sharing!
comment in response to
post
It’s not only about out-of-sync, bumping versions in a single file instead of a dozen of package.json is also better for reviewing and diffing.
If one already uses catalogs in their monorepo, leveraging it to also categorize deps does not introduce a lot trade offs
comment in response to
post
I see. But are you rejecting the idea of catalogs at all, or do you see a better solution for this? (for monorepo versions management and categorization)
comment in response to
post
Dependabot and Revonate already support it. And you can try taze to bump the versions in CLI
comment in response to
post
> deviates from the initial reason pnpm catalogs was introduced
Hammer is not designed for open walnut, but could be a nice tool to do that when you don’t have a better tool around.
I don’t think there is a problem to use a tool within its designed functionality.
comment in response to
post
> as if newbies don’t already have trouble figuring prod/dev
Isn’t that the problem I am trying to mention? Prod/dev doesn’t make sense for apps that’s why it’s hard to understand.
> tradeoff
What’s the tradeoff? If it’s about tooling, that’s something we should help improve.
comment in response to
post
Yarn has plans to add similar support for catalogs as well, which will help make this a consistent staple across package managers in the ecosystem.
github.com/yarnpkg/berr...
comment in response to
post
Vite Devtools are in the works! 👀
@antfu.me is leading this project which was made possible through a partnership between @voidzero.dev and @nuxtlabs.com.
Plans include plugin pipeline inspection, bundle analysis, and more. For entire Vite ecosystem!
Sneak peek below
voidzero.dev/posts/voidze...
comment in response to
post
Glad it helped! Thanks for making it! 😆
comment in response to
post
It was great to catch up with you again. Thanks for organizing this awesome event, I enjoyed it so much! And everyone is so nice and friendly 💚
comment in response to
post
share.transistor.fm/s/4be1b04c
Mentions include @michigantypescript.com @bluwy.me @antfu.me @storybook.js.org @marvinh.dev @pi0.io @netlify.com @11ty.dev and many more!
comment in response to
post
Thank you Kanon!
comment in response to
post
行きたい！でももうすぐ売り切れそう？！めっちゃ人気だね。
comment in response to
post
Thank you, hashrock-san! Let's find some time to meet! (🙇)
comment in response to
post
Oh oh! I am sorry I messed it up! Hashrock-san! 🙇🙇🙇
comment in response to
post
🐱🌸
comment in response to
post
よろしくお願いします🙇
comment in response to
post
And of course, I am not saying "Cursor is bad at engineering" or anything. Actually, I'd say their engineering is very impressive, as they managed to make the auto-completion so seamless and intuitive. I believe they have a strong engineering team behind (surely not AI) 😄
comment in response to
post
I have a few projects that consistently freeze upon opening, on the latest Cursor. I have to switch back to VS Code for those projects.