Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

When --from-lock is used, --no-dev becomes a no-op

Offen
  • Stimmt etwas nicht?
#778 2 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@asgrim arbeitet bereits daran.

Seit 16.10.2026.

  • #779 von @asgrim — offen

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

maintainer investigating

What are you trying to do?
When you have a pie.lock file, and you use the --from-lock option, all dependencies are installed regardless of if they are in require-dev in composer.json or pie.json (manually set, as I can't see any way to install as dev with pie install.

For reference, this is where we have a number of AWS Lambda functions that share a common Dockerfile; but not all of them need the same extensions. We want to use pie.lock to simulate what was previously possible with --allow-non-interactive-project-install where we can specify in the application repository (in composer.json or similar) which extensions to enable.

What platform, and PIE version are you using?
OS: Amazon Linux release 2023.12.20260930 (Amazon Linux)
Pie:

PHP Installer for Extensions (PIE) 1.5.1, from The PHP Foundation
--
You are running PHP 8.5.9
Target PHP installation: 8.5.9 nts, on Linux/OSX/etc arm64 (from /root/.phpenv/versions/8.5.9/bin/php)

Steps to reproduce the issue

  1. Run pie install including select arguments for your packages
  2. Copy generated pie.lock to correct location on machine where extensions need to be installed
  3. Optionally copy generated pie.json to correct location, updating extensions from require to require-dev as required
  4. Run pie install --from lock --no-dev

What do you expect to happen?
Ideally, the requirements listed in require-dev in composer.json or pie.json are not installed; but at a minimum if the --no-dev flag is a no-op then it should warn that this is the case.

What is actually happening
No warnings given, and all normal/dev extensions are installed.

Complete logs/output
Complete error messages and/or logs, including stack traces (hint: use -v for verbose), but please redact sensitive information.

Anything else?
other information that might be helpful...

Vorherrschende Sprache
PHP
Sterne
2k
Forks
75
Ø Merge
20 Std.
Gemergte PRs (30 T.)
16

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus php/pie

Alle Issues in php/pie

Ähnliche Issues

Weitere Issues zu PHP

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.