Excited to announce the release of the @spatie_be package pdf-to-image v3.0! Newly designed API, PHP 8.2+ support, bug fixes, enhanced performance, and more!🚀 https://t.co/X1MzlWjMRH
A year in the making and almost ready to ship: GitHub Curator is heading to production soon to help developers discover great projects worth their time.
Today I’m sharing a look at the tasks dashboard the behind-the-scenes control panel that powers all the background work in the app.
@GithubProjects #opensource #oss #github
I’m attending JSNation – the main JavaScript conference of the year. You may join me there for free with 10k other JS engineers and 40+ great speakers. Just follow this badge.
#javascript
https://t.co/jXwy3GtRwc
#jsnation
Get ready for:
✅ Easy management of complex, multi-step tasks
✅ More autonomous AI collaboration
✅ Deeper project understanding
✅ A serious productivity boost
🤖 Try out the new GitHub Copilot coding agent
https://t.co/LjPJEvQh3C
@devgummibeer@freekmurze Thanks for the feedback @devgummibeer, I think you make a really valid point! While I don't completely agree, I'm going to update the article to reflect this perspective, as it's a completely valid argument. 🙏👍
We're slowly closing in on releasing our 500th open source package! 📦
Over the past decade, we've established a set of guiding principles for what makes a great package.
1. Easy and fun to use
Put effort into making our packages as user-friendly as possible. Ultimately, a package should be fun to use.
2. Excellent documentation
Invest time in creating excellent documentation. Makes it easy to discover what a package does and what all the features are.
3. Well-tested
Provides yourself and others with proof that the package code behaves correctly and works under all conditions.
4. Readable
Structure and write our code in such a way that others can easily understand what is going on. Choose names of variables, functions and classes with care.
5. Flexible
You can’t imagine every scenario your code will be used in, so make packages as customizable and extensible as possible. Structured code in small functions and classes that can be overwritten or extended.
6. Small scope
Keep the scope small. Prefer a small package with one very polished feature over a large package that tries to cover all possible edge cases and variations of a problem.
7. Up to date
Try to keep your package up to date in the long run. When maintaining a Laravel package, tag a new version for each major framework update.
👀 Looking for that elusive bug is difficult, even with a great tool like Ray.
💡 But when you finally find the bug, you'd better celebrate!
🎉 You can call `ray()->confetti()` to get the party started. Check our blog post in the comments to see it in effect.
@spatie_be Hey @Spatie, don't forget to mention that developers working with node.js, javascript, or typescript, including vue and react applications - Ray has got you covered!
https://t.co/Uc387KRNXA
https://t.co/oDdN070lmo
I'm thrilled to announce that, finally, vue-ray 2.0 has been released! It features full composition api/script setup support, the most requested feature 🎉https://t.co/Uc387KRNXA
Make sure to check out Ray at https://t.co/Uj4ZrjUtCH!
@freekmurze@spatie_be@vuejs
I'm happy to announce that after a long delay, version 2.0 of node-ray has been released! Ray by @spatie_be is a great debugging tool - check it out if you haven't yet. https://t.co/aX6lUhvgrJ @freekmurze@PermafrostDev
I've just developed an innovative application that simplifies the process of generating deploy scripts for Laravel Forge! 🚀
🔗 Check it out here: https://t.co/7zPYR7gPZW
I'm eager to hear your thoughts and feedback. Your insights are invaluable in making this tool even better!