matejcerny.dev
developer, photographer, videographer
34 posts
52 followers
72 following
Getting Started
Active Commenter
comment in response to
post
You could try looping through the layers, reading and merging each config, then creating a virtual file for the final layer. But I might be misunderstanding - ideally, the original module should handle this nuxt layers support.
comment in response to
post
I haven’t used Nuxt Content much, but doesn’t it already merge the config defined in nuxt.config.ts?
As for merging the config from Vueform, I think the module authors should add support for merging configurations between layers - if they haven’t already.
comment in response to
post
What do you need to use the config files for? How is it different from merging nuxt.config.ts?
comment in response to
post
As long as it's not a paper calendar, I think you're good
comment in response to
post
Thank you for visiting! Hope you had a good flight 😊
comment in response to
post
I’m personally still putting off updating to Tailwind v4. I’m waiting for better language server support and ESLint rules.
comment in response to
post
This is amazing! Much sooner than I expected!
comment in response to
post
I'm conflicted… My Apple Watch keeps telling me to hydrate more.
comment in response to
post
i read it as “nuxt” at first
comment in response to
post
I prefer the OG way of <template> first, since I find it easier to differentiate what component I'm looking at when quickly glancing over the template, rather than having to go through the logic in the script.
Also, when cmd+clicking through multiple components, it is better to have template on top
comment in response to
post
Thank you so much, Daniel ❤️
comment in response to
post
You're an inspiration for me on so many levels. I admire your productivity, kindness, positivity, friendliness…
It really shows that you love coding, which I feel the same way about, and it's very nice to have the opportunity to talk to like-minded people.
comment in response to
post
This was a great read!
We appreciate your work and involvement with the community tremendously 🙏 Thank you for everything you do, and wish you all the best in the new year! 😊
comment in response to
post
Merry Christmas! 🎄🎁
comment in response to
post
missed the "next year" joke 😄
comment in response to
post
const {
onClick,
} = defineProps<{
onClick?: () => any
}>()
const isLoading = ref<boolean>(false)
async function handleClick() {
try {
isLoading.value = true
await onClick?.()
} finally {
isLoading.value = false
}
}
comment in response to
post
I actually do this all the time for async button callbacks, for example. So that they can handle the loading state internally.
comment in response to
post
Happy birthday, Alex! 🥳🎉
comment in response to
post
Christmas songs going strong already?
comment in response to
post
Happy birthday! 🎂
comment in response to
post
Feel you
comment in response to
post
Also, I prefer the way the timeline refreshes in “that other app”. Having to scroll all the way up to refresh, then scroll back down and remember which post I've already seen in the “Following” feed to stop scrolling is a little inconvenient.
comment in response to
post
Love it here! Though, here are some things I really miss:
- 🔖 bookmarking posts (bookmark groups, search)
- 🚨 notifications for people's posts
I also think it would be nice to keep track of people's old handles and either replace old mentions with new ones or make the old ones work.
comment in response to
post
Sign me up! 😄
comment in response to
post
Don't forget about @dejavue.fm ✨
comment in response to
post
Thanks for the heads up!
comment in response to
post
Ok, but why isn't watch deep by default then?
comment in response to
post
I have to say that I absolutely love the way the handle system works