composer-deps-analyzer

composer-deps-analyzer copied to clipboard

Hi @schmittjoh, Composer installs * require dependencies of all package * require-dev dependencies of only root package But the composer deps analyser analyses * require dependencies of all package (ok)...

kassko

Add strict isOnlyDevDependency() to check for dev dependencies

2

The current `DependencyEdge::isDevDependency()` is a bit ambiguous with regards to mixed dev- and non-dev-dependencies: Source packages that list the dependency in both "require-dev" and "require" will only create a single...

clue

Test suite should not rely on triggering composer

4

Currently, the test suite uses composer to temporarily install some packages, analyzes the resulting package set and then removes the packages again. This makes the test suite slow to run,...

clue

[wip] Add option to ignore dev dependencies

1

- [x] Implementation - [ ] Tests Resolves #8

clue

The current behavior is a bit ambiguous with regards to mixed dev- and non-dev-dependencies: Source packages that list a dependency in both "require-dev" and "require" will only create a single...

clue

Currently, we analyze every single package and add all of them to a single graph, no matter if it's a dev and non-dev dependency. Instead, I'd like to propose we...

clue

I want the `analyze` function [here](https://github.com/schmittjoh/composer-deps-analyzer/blob/6e72a866c40a98e63efb6bb059a2bbaadcb8aa15/src/JMS/Composer/DependencyAnalyzer.php#L32-L39) to support an optional field which enables looking into `$dir` recursively and add the packages by calling `createPackage` for each directory with a `composer.json`...

vishwarajanand

Add feature to exclude packages

1

I want to exclude "some" packages (but not all dev dependencies) from the generated graph, can I have something like this? ```

vishwarajanand