Can't install using Composer

[lewebsimple]

Description

When installing using Composer, I get the following error:

In ClassMapGenerator.php line 137:
                                                                                                                                                                                                      
  Could not scan for classes inside "wp-content/plugins/wp-graphql-headless-login//vendor-prefixed/" which does not appear to be a file nor a folder  
                                                                                                                                                                                                      

Any idea?

Steps to reproduce

Using this composer.json file:

{
  "name": "lewebsimple/test",
  "type": "project",
  "repositories": [
    {
      "type": "composer",
      "url": "https://wpackagist.org"
    }
  ],
  "config": {
    "allow-plugins": {
      "composer/installers": true
    },
    "optimize-autoloader": true,
    "preferred-install": "dist",
    "sort-packages": true
  },
  "require": {
    "axepress/wp-graphql-headless-login": "*",
    "wpackagist-plugin/wp-graphql": "*"
  }
}

Additional context

No response

Plugin Version

0.4.4

WordPress Version

6.8.3

WPGraphQL Version

2.3.6

Additional enviornmental details

No response

Please confirm that you have searched existing issues in the repo.

• Yes

Please confirm that you have disabled ALL plugins except for WPGraphQL and Headless Login for WPGraphQL

• Yes
• My issue is with a specific 3rd-party plugin.

[stefan-stanic]

Hey, having a similar issue, did you manage to fix it @lewebsimple ?

[justlevine]

@stefan-stanic for now add a post-install-cmd to cd into the plugin folder and composer install --no-dev

[lewebsimple]

Yeah recursive composer install is a real PITA, I usually end up republishing the package with the vendor folder included on my private packagist repo.

[stefan-stanic]

@justlevine I'm not sure that will work for my setup.

My deploy is via docker
RUN gosu www-data composer install --no-dev --no-cache

And post-install-cmd would never execute because it will fail at composer install.

[justlevine]

@stefan-stanic @lewebsimple it's probably about to get even worse once I cleanup and ship #181 , since it won't just be the composer deps that need post-install prefixing, but the admin js that needs an npm run build (although at least that one won't fail on a --no-dev) 🤔

• If you don't need to worry about semver, you could point composer.json at the release zip. I havnt tried myself, but I think if you use the versioned link dependabot might be smart enough to semver-update it for you.
• Similar approach would be to avoid composer entirely in that case and just RUN {...} wp plugin install {url to evergreen/versioned dist} --allow-root --activate
• Mid-term I'm planning to add PUC but that won't help yall with installing just updating from the dash/cli. Eventually the repo will be submitted to dot-org - which would solve things via wpackagist.org - but can't promise when that will happen (I figure we'll need a breaking code refactor once SAML and 2FA are implemented and then I can submit, but need to scape free time/a sponsor to let me focus on either of those)

I haven't used it before myself, but I'm open to exploring a solution like https://github.com/pixelfear/composer-dist-plugin (IIRC statamic uses it) if somebody wants to open a PR. Also happy to explore other suggestions that arent version-controlling vendor-prefixed