Marc Henry Schultz

yes i discussed somewhere a `package://` resource wrapper, which can be used to acess the Resource folder too https://github.com/neos/neos-development-collection/issues/3507#issuecomment-1025468376

I think this issue becomes obsolete with the new CR?

thats not true there is a check made if the extension is loaded: https://github.com/neos/neos-development-collection/blob/f8e64887233eda2e4afd1a1a7327429b7694dd22/Neos.CliSetup/Classes/Infrastructure/ImageHandler/ImageHandlerService.php#L49 i have no clue about this vips but i have the feeling that you have this...

if its not a php extension the above check: ``` var_dump(extension_loaded("vips")); ``` will never pass - so vips would be never selectable and yield no errors... im missing something here...

> i have the feeling that you have this php extension installed but not installed the php library mentioned. and we dont check for this case... so as i guessed....

hmm but the call to `$imagine = $this->imagineFactory->create();` would still fail right? we need to catch it or is this fixed with your pr and i dont see it? :see_no_evil:

Due to the parser rewrite this PR would need to get updated. - I would step in here ;) The parse time exceptions are currently great (they show line number...

> So apparently the autoload-dev section only applies when inside the root composer.json (https://getcomposer.org/doc/04-schema.md#autoload-dev), which in turn means we need to sync autoload-dev sections of all packages into our dev-distribution(s)....

sure but why dissallow it - its a [regression](https://github.com/neos/neos-development-collection/pull/3847#issuecomment-1192828741).

Noice. Early comment: rector seems to like to write exception codes in the format like `1_348_750_840` which i think is weird ...