You might have noticed that the newsletter's design changed a bit.
I did a large refactoring of the code, and now I use Vue Mail instead of my custom rendering solution that was based on Nuxt Content and mjml.
As a result, I have a much more maintainable code base and a well-tested rendering library for my emails. Let me know if you encounter any issues with the new issues.
👉🏻 JD modified VitePress to create a similar experience like Nuxt Studio provides, where you can just write the content and it shows you the preview of the content in real time.
You may currently use process.serverprocess.server or process.clientprocess.client in your Nuxt apps to determine if your code runs on the client or server side.
This API is now deprecated, and you should use Import Meta instead:
if (import.meta.client) {console.log('Client side')}
if (import.meta.server) {console.log('Server side')}
Sunday, January 5, 2025 Update: Bluesky images work again and thus the Great Art on Bluesky channel is back. If you're on Bluesky please subscribe. # The crazy thing about Bluesky's API is they took already standardized things like links and enclosures, and after 20+ years came up with new definitions. Makes our apps more expensive to maintain, and we waste time and human wear and tear on stupid bullshit make-work. Developers are people, and our work is already horribly overly complex, we're working at the edge of comprehension, and what the fukc let's throw some more unnecessary complication into the mix. Arrogance, narcissism, whatever the source is, it's not a good way to introduce yourself. And, even better, after you go through the maze they break it, with an error message about legacy blob bullshit. They've already done this, and they're just getting started. It's why I say they should just adapt to RSS instead of trying to forc...
评论
发表评论