Anton Marin

@Adirelle is issue related to #110

I can't use composer global installation in my CI pipeline, so can you publish docker image? I can create pr with Dockerfile

I see now. Looks strange )) This way creates some difficulties with building. Mb docker image would be more simple to use?

I mean, i can create PR with Dockerfile with tool installed the way you offered. Then maintainer can publish it in dockerhub. I think it would be simple to use...

Update: I tried the way you offered in #issuecomment-878953040 and got the same error

``` sh-4.2$ pwd ${project_folder}/tools/composer-require-checker ``` ``` sh-4.2$ php vendor/bin/composer-require-checker check --ignore-parse-errors -vvv --config-file=${project_folder}/composer-check-requirements.json ${project_folder}/composer.json ComposerRequireChecker 3.3.0@4063254c611acf34f1c15b29b6bcc47d2e7a9a9e Collecting defined vendor symbols... In LocateASTFromFiles.php line 50: [RuntimeException] Parsing the file [${project_folder}/vendor/doctrine/mongodb-odm/lib/Doctrine/ODM/MongoDB/Aggregation/Stage/GraphLookup/Match.php] resulted...

>Problem with that is keeping an updated composer.lock that works for everyone. People running on PHP 7.4 and people running on PHP 8.0 have different requirements (like this bug shows)....

I see now. So seems like there are 2 ways to fix my error: 1. Identify why --ignore-parse-errors didn't work in this case 2. Implement a way to exclude some...

If you have docker hub account to publish i can create PR with Dockerfile and workflow

sorry, not able to test it. is there some kind of doc to understand how to use it?