Gareth Jones

I'll leave that to you as I suspect you'll have more pull :-)

> Can you help me understand what withoutAutofixOutput is for That was a helper which already existed in one of the tests, so I decided to pull it out as...

Just to add an update from my end: I don't mind continuing to help on this, but I couldn't make progress on the remaining issues at least some of which...

> How can I help see this change through There's a number of things that need actioning which I've eluded to in https://github.com/import-js/eslint-plugin-import/pull/2996#issuecomment-2115906241 - there's also some requirements from @ljharb...

It seems like our capistrano based deployments are relying on this, which makes sense (especially since we're not sharing `node_modules`, which maybe we should 🤔), so we'll want to include...

You can resolve this by updating the dependency e.g. `npm update js-yaml` - Jest does not need to do anything for this, and in fact the referenced commit just updates...

So I think I've gotten here from seeking the same underlying problem that @yegor256 is working on, but I'm thinking that using `disable_net_connect` and `enable_net_connect` is not the right solution...

Can you name the package(s) with the erroring versions? My understanding is that composer requires versions to be semantic

Cool thanks - if you can, it would be good if you could provide a small but complete lock file reproducing the error but otherwise now that I've got the...

@3asm could you speak more about how you generated this, including the composer version and json file? I suspect this is technically invalid (or maybe not natural?) - using this...