4 posts tagged with "Devtools"

Never thought you'd need to handle database migrations in Node.js? Me neither. Anyway, here’s one way to do it. Oh, and I think Node.js blog posts need emojis, right? 💯💡

Since migrating to my Windows 10 & WSL2 setup a few years ago, I regularly try to reclaim disk space from my WSL2 setup by following the steps outlined in Scott Hanselman's blog post. However, this time it did not work as expected.

This blog post has been sitting on my desk for quite a while but due to a lot of work in the last weeks I was not able to finish it earlier. Luckily, I found some time during my travels to finish the blog post and share my findings on the "require-dev gone wrong!" problem. While some people thought the former blog post was mostly click bait or proposed a "fix" which does not actually solve the general problem, I actually got a lot of good feedback on twitter. Even an issue for Composer was created to discuss the problem even though it was closed by now.

For a long time, I have been advocating to make use of require-dev to install development tools locally. We use this on a daily basis to install tools like Phing, PHPUnit or phpDocumentor locally for each of our (customer) projects. Given that our focus is on custom projects, this absolutely makes sense. I do not want our projects to use an old version of a given tool or update all our projects constantly to use the latest version of all the tools involved. In addition to that, a simple composer.phar install in the project root should be sufficient to install all dependencies required to build and run the project.