AI is incredibly good at writing great tests, then adding special cases matching these tests in business logic to make them pass.
25.04.2025 01:53
👍 1
🔁 0
💬 0
📌 0
AI is incredibly good at writing great tests, then adding special cases matching these tests in business logic to make them pass.
And for Vite integration: we are now passing all relevant tests in github.com/rolldown/vite, the temporary fork of Vite that runs on Rolldown instead of esbuild / Rollup. Expect a proper release early 2025!
I'm picking back up a project I started in 2017 (I set myself a deadline of 2037 at the time).
Playing around with this demo of abstract interpretation I wrote 4 years ago.
I have no idea how it works anymore, and it's probably incredibly inefficient, but keen to dive back into it!
If you'd like a bunch of it is also published as OSS NPM packages (with absolutely zero documentation for now).
Been out of the social media game for a few months. Is this where the cool kids hang out nowadays?
Refactoring the Preview.js codebase to separate out *detecting components* from *previewing components*.
This will simplify the codebase (better separation of concerns).
It will also lead to a new API to get a list of all components (and their prop types) in any codebase.
Is there already a VS Code extension to see a list of all your components and navigate to their definition in one click?
What would you use that for?
To be fair, I'm a lot more proficient at TypeScript than I am with Kotlin, so that might play a part too.
I tried ChatGPT, and it very confidently invented a bunch of methods that don't exist.
Implementing a feature for the Jetbrains plugin always takes me at least five times as long as the equivalent for the VS Code extension 🙁
A lot of that involves desperately searching for code samples on GitHub because IntelliJ Plugin SDK docs are so minimal.
Preview.js for IntelliJ/WebStorm no longer blocks the main thread on a periodic basis, yay 😅
More perf improvements coming soon, once I get all tests green ✅
Have I mentioned how poorly documented the IntelliJ Platform Plugin SDK is?
It's the third time I'm rewriting the same functionality because they keep changing their API.
Absolute nightmare.
OK Google, set the volume to 4
Google: volume is now 10
Preview.js v1.22 has already been out for a few days, but here's the full blog post with the juicy details 🥳
https://previewjs.com/blog/previewjs-v1.22
Thank you, reposted the correct link!
I finally made a YouTube video!
Hopefully the first of many.
Let me know what you think, like and subscribe! 😁
https://www.youtube.com/watch?v=v7qOmg7xgMM
I should really be recording a YouTube video and I was running out of procrastination ideas, so I cleaned my home office 🤩
I have a silly TypeScript question.
https://tinyurl.com/2bpemx6m
I got three new paying customers in the last couple of days 😊
This is despite making Preview.js Pro free for everyone for 30 min/day a few weeks ago.
It felt like a risky decision (compared to a trial with credit card) but I'm glad I did that!
Just finished redesigning the homepage 🥳
I added screenshots for each of the features, which should hopefully make it a lot clearer.
https://previewjs.com
Just finished recording a new short video for the http://previewjs.com homepage.
It showcases the "Save as Storybook story" feature, which is finally ready for everyone to use across all frameworks!
Now I just need to update all the docs 😬
Here's the news I couldn't wait to share...
I'm joining Canva as a Frontend Infra Specialist!
The role is perfectly aligned with my developer happiness and frontend interests 🤩
I'll work part-time so I can continue improving Preview.js too 👀
Writing tests can be draining.
One weird trick I use to get over the mental barrier: write a TODO comment listing all the test cases you'd like to write.
This effectively breaks it up into much simpler tasks, and seeing the list go down helps with motivation.
Hello, World!
