haoqun.dev
@vuejs.org core team member.
@vite.dev core team emeritus.
Worked on JS tooling. Learning something new.
https://haoqun.dev/
52 posts
336 followers
922 following
Regular Contributor
Active Commenter
comment in response to
post
Can't believe scoped packages wasn't a free feature of npm until 2017-03-22 blog.npmjs.org/post/1587182...
comment in response to
post
Have you tried `v-memo`?
comment in response to
post
@rspack/core does not have a postinstall script, so it won’t be in the list in the first place. If the attacker adds one, it won’t be executed by default.
This feature mitigates risks like this, and that’s it, it’s not designed to prevent all possible attacks.
comment in response to
post
Note it's not about their Node APIs (so Vite isn't affected), just when executing the binaries (i.e. `pnpm exec esbuild`) there will be a performance hit.
comment in response to
post
In my experience this new default doesn't break many projects.
But it might slow down some native packages a bit.
For example, packages like esbuild, lightningcss-cli try to optimize their binaries in the postinstall scripts; these will no longer be executed by default: github.com/evanw/esbuil...
comment in response to
post
?? The link preview is still available even though I deleted the link? Interesting feature/bug…
comment in response to
post
And in case you still want that username, you can temporarily change your handle back and forth to reserve it. This feature was introduced about a month ago: bsky.app/profile/bsky...
comment in response to
post
Sure, that sounds interesting! What features do you have in mind?
comment in response to
post
Yes, very helpful!
It's major inspiration for me to start this list, as well as LavaMoat, and I have put links to both of them in the README.
comment in response to
post
To amplify the message maybe we can add codenames to minor releases, while attach nothing to the major ones, so that only the minor releases are cool?
comment in response to
post
The intrusive design is mostly due to the intrinsic complexity that makes overriding rules in plain array configs almost impossible without knowing the underlying implementation. Type-aware linting in Vue + TypeScript needs a complete overhaul… which I'd like to work on after this stop-gap measure.
comment in response to
post
The root causes may differ - so they are not labeled as duplicates. However, the similarity in issue descriptions suggests that some bugs could have be avoided if sufficient tests had been added earlier.
comment in response to
post
Good tips! Just a small correction: it’s recommended to use `<PascalCase>` in templates as well (with the exception of in-DOM templates) to distinguish Vue components from custom elements.
More info here: vuejs.org/guide/compon...
comment in response to
post
I think you can create one from the Starter Pack via graze.social
comment in response to
post
I’ve seen quite a few similar complaints this year, often related to the VS Code `useVsCodeWatcher` setting (recently renamed to `watchOptions`), so you might not see many in the TypeScript repo.
Here’s a helpful write-up: github.com/microsoft/Ty... It might have been fixed since, but I’m not sure.
comment in response to
post
Here: github.com/rolldown/vit...
comment in response to
post
Enforced in EU only.
comment in response to
post
PascalCaseFileNames
comment in response to
post
Other platforms have “For You” feeds for similar reasons, but they've done a poor job. On Bluesky, we have the chance to do it right, and by ourselves.
comment in response to
post
It's just like real life - at crowded parties, we naturally focus on close friends rather than leaving. Same with Bluesky - you can be selective about whose posts you see more of.
comment in response to
post
Ah, I highlighted the wrong sentence. 😂 It's also mentioning "Lucide React for icons", not just logos.
comment in response to
post
Source: github.com/bluesky-soci...
comment in response to
post
But the tracking *is* different: 0.25px tracking is applied when using the system font (0 if you switch to Inter).
@esb.lol I'm curious about what's driven this design decision. Would you mind providing some insight?
comment in response to
post
Good news: they call themselves “SkyWatchApps” on the other site. No conflicting branding at all!
comment in response to
post
It’s always a pity for me that Community Notes’ original name, “Birdwatch”, didn’t stick around. Can we brand it as “Skywatch” here? I like names with their own characters.