heiglandreas, 15 days ago

@pieceofthepie Yes! (or separate composer.json files per tool)

pieceofthepie, 15 days ago

@heiglandreas It'd be lovely if development dependencies got their own namespace.

At least that would mean not having to upgrade my codebase to support a newer test tool.

heiglandreas, 15 days ago

@pieceofthepie I'd rather use a separate composer.json. Those aren't dependencies of your application. Just tools...

Separate Namespace doesn't work (apart from in scoped phars) as those tools also use dependencies that your project might use. How should that lib know whether it's used in a tool or a project?

pieceofthepie, 15 days ago

@heiglandreas "Those aren't dependencies of your application. Just tools..."

Fair, but also, if I remove development dependencies from the my projects if they're just tools then those projects no longer have development dependencies.

Which I guess leads me to "what are development dependencies for if not things needed for development?"

heiglandreas, 15 days ago

@pieceofthepie Exactly. Only for development. Your code also earns money without them.

But by adding them to the dev-dependencies you are tying the code that earns money to the tools you only need for development.

By using separate composer.jsons (or PHARs) you can use the tools without tying your code to them and their dependencies.