Nate Lab

It's not an easy problem to solve sadly, on the top of my head the easiest solution would be to use Libraries.io API to get the dependent repositories and filter the result. It's far from ideal though.

Here is the result I got when trying it for `pure-color` : gist.github.com/IonianPlaybo...

It just got merged 🎉

I am very glad to know that soon I will be able to migrate from `vue-docgen` to get a better autodocs.

Oh I totally missed that, my bad.

Here's hoping that it gets fixed one day.

The text "come as you are" in all caps, written 8 times from top to bottom on a black background. The fourth one from the bottom is filled with a gold to deep pink gradient, while the others only have an outline of the same colors. There is no wave-like distortion applied to the text.

Looks very cool. 🔥

Just to let you know, I had to open it on Chrome to see the nice wavy effect, it does not work on Firefox. (v132.0.2 on MacOS)

Elk A nimble Mastodon web client

Two years ago, 200+ of us collaborated to build elk.zone. Would you be interested in an Elky Nuxt PWA Client for Bluesky? Elk has markdown code blocks.

Do you enjoy tinkering with @vite.dev, @vuejs.org, @nuxt.com, @vueuse.org, @unocss.dev, @shiki.style, the @bsky.app API? Would you like to help us?

Hello, I would be glad to help out if I can 😊

My main problem right now is that this sadly doesn't work with librairies that define CSS vars for dark/light mode values, since you can't override their variables definition to use another selector.

I have opened a discussion on GitHub to improve this, feedback welcome.

github.com/tailwindlabs...

Tailwind Play An advanced online playground for Tailwind CSS that lets you use all of Tailwind's build-time features directly in the browser.

Very excited about @tailwindcss.com's beta release for v4, it looks amazing.

I played a bit with it yesterday and got a working "dark/light mode but overridable localy with a data attribute" with only CSS!

Here's the code if you are curious:

play.tailwindcss.com/CrjRI17OxV

Feature request: I would love to be able to just click a username on the Android app to copy it.

It's really a pain to get the handle of other accounts to link them in a post. I ended up using Bluesky on a browser to have access to the text, then pasting it in the native app. 😣

(disclaimer: I'm not a Vapor contributor at all, I'm just following the progress from times to times.
I'm also very excited to see the progress being made, hyped to see it released someday. 😊)

VitePress on Vapor · Issue #289 · vuejs/vue-vapor Repo: https://github.com/sxzz/vitepress-vapor self reference class inherit scope id inherit <component> createBranch API valid slot destructure in v-for @vue:beforeMount hook Transition component a...

The latest news was supporting Vitepress, issue here: github.com/vuejs/vue-va...

It's in active development right now.

The best person to follow for updates would be @sxzz.dev, but he's more active on X at @sanxiaozhizi.

He recently was sponsored by Vue Fes for his work on Vapor, which is great. It's hard to believe that before that he was struggling to get a decent income.

Cover art of the board game Root, described as "A Game of Woodland Might and Right"

Oh yeah this is a cool game. Pretty unique and fun.

I've been looking into this one recently. At a first glace, it seems like it definitely take some time to read all the rules and explain them to all the players, but it could be worth it.

Vue: fix `vue-component-meta` docgen HMR not working by IonianPlayboy · Pull Request #29518 · storybookjs/storybook Closes #27514 What I did Currently, the vue-component-meta plugin is only running when Storybook is initially launched, but it never updates afterwards. The only way to get the updated values in...

I've opened a couple weeks ago a PR on the @storybook.js.org repo to fix the docgen HMR for @vuejs.org components.

I'm pretty new to handling HMR though, so it certainly could be better.

If you are familiar with Vite's `handleHotUpdate` method feel free to review.

Link: github.com/storybookjs/...

I guess my ideal solution would be a badge/icon that is out of the flow of the page, and that could be moved/dismissed by the user?

This is what would make the most sense to me, but it might be impossible to find the right design; either too discrete or too much in the way with no in between.

Visually distinguish between build environments (dev, qa and production) During the development of our mobile applications, they go through a development phase, a QA phase and are finally released into production. We create separate builds of the applications for each

The best discussion I could find online on the matter is this thread: ux.stackexchange.com/questions/79...

It's about mobile apps, but it could apply for a web app as well.

The option 4 & 5 looks the most promising to me, but I'm not convinced that these are the best way to solve the issue.

How do you visually dinstinguish between dev/staging/prod envs in your apps ?

We had a thin banner at the top of the page for dev and staging in my previous job, but it created an annoying inconsistency between envs that was hard to keep in mind.

It forced us to hotfix the prod CSS more than once.

Hello blueskies!

I've never been very active on social medias before, but I feel like trying here; the vibes are good.

My posts will often be about web dev stuff so if you're cool with that feel free to follow. I promise I'll do my best to remember once in a while to share (hopefully) cool things.