[GH-ISSUE #628] Composer lockfile problem #427

Closed
opened 2026-02-25 21:35:00 +03:00 by kerem · 2 comments
Owner

Originally created by @ksieluzycki on GitHub (Sep 26, 2022).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/628

Originally assigned to: @jasonmunro on GitHub.

Hello,

During installation I encountered following error from composer install:

No vendor dir present, checking platform requirements from the lock file
In Locker.php line 324:
[LogicException]
No lockfile found. Unable to read locked packages

I thought it should create composer lock if necessary, but it didn't. I also tried composer update, but it also shows same error and does not create composer lock.

It looks like check-platform-reqs is invoked as pre-command and it requires composer lock. I just edited composer.json:

"scripts": {
    "pre-install-cmd":  "",
    "pre-update-cmd": "",

After that composer install completed succesfully.

Tested on:
Composer version 2.4.2 2022-09-14 16:11:15
on Debian 11.5 and on Artix

Regards,
Krzysztof

Originally created by @ksieluzycki on GitHub (Sep 26, 2022). Original GitHub issue: https://github.com/cypht-org/cypht/issues/628 Originally assigned to: @jasonmunro on GitHub. Hello, During installation I encountered following error from composer install: No vendor dir present, checking platform requirements from the lock file In Locker.php line 324: [LogicException] No lockfile found. Unable to read locked packages I thought it should create composer lock if necessary, but it didn't. I also tried composer update, but it also shows same error and does not create composer lock. It looks like check-platform-reqs is invoked as pre-command and it requires composer lock. I just edited composer.json: "scripts": { "pre-install-cmd": "", "pre-update-cmd": "", After that composer install completed succesfully. Tested on: Composer version 2.4.2 2022-09-14 16:11:15 on Debian 11.5 and on Artix Regards, Krzysztof
kerem closed this issue 2026-02-25 21:35:00 +03:00
Author
Owner

@jasonmunro commented on GitHub (Sep 26, 2022):

Appreciate the feedback. We have been discussing removing this from the composer.json file as I ran into the same issue. In my case I had scripted an update process that was calling composer as root. Once I modified that it started working even with the check-platform-reqs active.

<!-- gh-comment-id:1258278336 --> @jasonmunro commented on GitHub (Sep 26, 2022): Appreciate the feedback. We have been discussing removing this from the composer.json file as I ran into the same issue. In my case I had scripted an update process that was calling composer as root. Once I modified that it started working even with the check-platform-reqs active.
Author
Owner

@marclaporte commented on GitHub (Nov 1, 2022):

Closing in favor of:

<!-- gh-comment-id:1297865185 --> @marclaporte commented on GitHub (Nov 1, 2022): Closing in favor of: - https://github.com/jasonmunro/cypht/pull/632 - https://github.com/jasonmunro/cypht/issues/597
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/cypht#427
No description provided.