Trigger.dev CLI 4.8.3 — minimatch makeRe incompatibility and nested tar security findings
Les mainteneurs répondent en général sous 1 jour
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Accessibilité débutants
- 8/100
- Type d'issue
- Refactorisation
- Clarté
- À clarifier
- Activité
- Active
- Stack technique
- nodejs, typescript
- Domaine
- build-system, security
Piste de recherche
The payload names dist/esm/build/externals.js, which imports makeRe from minimatch, and the dependency chain c12 → giget → [email protected]. The reporter's experiment failed and no fix is proposed, so the first step is a maintainer decision on the supported remediation path, not a code change. Done means maintainers have answered the five questions or a supported version has been identified.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
Provide environment information
Summary
We are requesting an officially supported remediation for security findings in the development dependency tree of [email protected].
The original CLI works with its declared minimatch dependency. The makeRe startup failure occurred only in an isolated, unsupported five-override compatibility experiment. That experiment FAILED and was NOT promoted.
Environment
- OS: Windows 10.0.26300.0
- Node.js: 24.14.0
- npm: 11.9.0
- Trigger.dev CLI: 4.8.3
- Trigger.dev SDK: 4.8.3
- npm lockfileVersion: 3
Original Security Audit
- 9 affected-package entries
- 1 critical, 6 high, 2 moderate
- 16 unique GitHub Security Advisories
- Production-only audit: zero findings
- SDK-only audit: zero findings
Affected dependency paths:
[email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
│ └─ [email protected]
│ └─ [email protected]
└─ @trigger.dev/[email protected]
└─ @prisma/[email protected]
└─ [email protected]
Isolated Experiment
Five unsupported dependency overrides were tested in a disposable copy:
- zod: 4.6.7
- minimatch: 11.0.1
- esbuild: 0.25.0
- [email protected] → tar: 7.5.22
- @prisma/[email protected] → deepmerge-ts: 8.0.0
The CLI failed with:
trigger.dev/dist/esm/build/externals.js:
import { makeRe } from "minimatch";
SyntaxError: The requested module 'minimatch' does not provide an export named 'makeRe'
The distributed Trigger.dev CLI uses makeRe in its externals builder. minimatch 10.2.6 provides the API, but 11.0.1 does not.
The nested tar dependency remained invalidly resolved:
[email protected]
[email protected]
[email protected] invalid: "7.5.22"
The exact npm resolver cause has not been established.
Results
- Original CLI startup: PASS
- Experimental CLI startup: FAIL
- Experimental audit: 4 affected-package entries, including 1 critical
- Backend mock tests: 19 passed
- Browser suites: 5 passed
- Production build: PASS
- Full experimental regression aggregate: incomplete
No experimental overrides were promoted.
Questions for Trigger.dev Maintainers
- Is there a supported CLI version or backport addressing minimatch GHSA-g3hv-75wg-m249 without breaking the makeRe API contract?
- What is the recommended remediation for c12 → giget → [email protected]?
- Are supported fixes available for the CLI's zod, esbuild and deepmerge-ts dependencies?
- Can you confirm the security status of bundled tar code in the @trigger.dev/build dependency chain?
- Is a separately pinned CLI workspace officially supported while keeping SDK 4.8.3?
We would appreciate a vendor-supported remediation path rather than unsupported major-version overrides.
No exploit has been demonstrated. The original dependency tree remains unchanged. Cloud is unconnected, MCP is disabled, and production booking is disabled.
Describe the bug
Trigger.dev CLI 4.8.3 has unresolved development dependency security advisories. The original CLI starts successfully with minimatch 10.2.6. However, an isolated, unsupported override to minimatch 11.0.1 causes CLI startup to fail because the CLI imports makeRe, which is no longer exported. A separate override targeting giget's nested tar dependency also resulted in an invalid dependency tree.
Expected: A vendor-supported, security-patched dependency combination that preserves CLI functionality.
Actual: The experimental overrides reduced audit findings from nine to four, but broke CLI startup and left one critical finding unresolved.
The experiment was not promoted. The original dependency tree remains unchanged. We are requesting official remediation guidance, not claiming the original CLI installation is broken.
Reproduction repo
No public reproduction repository is available yet. Minimal isolated reproduction steps are provided below; no private application source is required.
To reproduce
Environment: Windows NT 10.0.26300.0, Node.js 24.14.0, npm 11.9.0, [email protected], @trigger.dev/[email protected].
- Create an isolated disposable npm project with [email protected] as a development dependency and @trigger.dev/[email protected] as a runtime dependency.
- Install the dependencies and verify the original CLI version command succeeds.
- In a disposable copy, apply an npm override mapping [email protected]'s minimatch dependency to 11.0.1.
- Reinstall dependencies and verify minimatch 11.0.1 is resolved.
- Run the CLI version command.
Observed in our five-override experiment:
SyntaxError: The requested module 'minimatch' does not provide an export named 'makeRe'
The CLI imports makeRe from minimatch in dist/esm/build/externals.js. The original CLI uses minimatch 10.2.6, which supplies that API.
A separate experimental override attempted to replace [email protected]'s nested [email protected] with [email protected], but npm ls reported an invalid resolution. The exact npm resolver cause is unconfirmed.
Important: The isolated minimatch-only reproduction described above is proposed and has not been independently executed. The observed CLI failure occurred in the full five-override experiment. No overrides were promoted.
Suggested fix
No response
Additional information
No response
- Langage dominant
- TypeScript
- Étoiles
- 16.5k
- Forks
- 1.5k
- Merge moyen
- 1 j 15 h
- PR mergées (30 j)
- 17
Préparer son environnement
Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de triggerdotdev/trigger.dev
-
bug: retry.fetch ignores the caller's abort signal and retries aborted requestsPeut-être à nouveau libre Une pull request pour cette issue a été fermée sans être fusionnée. Ouverte
Difficulté 2/5 1-3 heures Accessibilité débutants 76/100
triggerdotdev/trigger.dev#5116 · 2 commentaires ·
Les mainteneurs répondent en général sous 1 jour
-
bug: Chat transport crashes on Safari < 17.4: AbortSignal.any is not a functionPeut-être à nouveau libre Une pull request pour cette issue a été fermée sans être fusionnée. Ouverte
Difficulté 2/5 1-3 heures Accessibilité débutants 83/100
triggerdotdev/trigger.dev#5098 · 2 commentaires ·
Les mainteneurs répondent en général sous 1 jour
-
bug: Side menu items lose their active state on detail pagesPeut-être à nouveau libre Une pull request pour cette issue a été fermée sans être fusionnée. Ouverte
Difficulté 2/5 1-3 heures Accessibilité débutants 72/100
triggerdotdev/trigger.dev#5088 ·
Les mainteneurs répondent en général sous 1 jour
-
bug: RBAC loader logs "plugin found but failed to load" when @triggerdotdev/plugins is simply not installedPeut-être à nouveau libre @itsfaryal l’a pris il y a 17 jours, et aucune pull request n’est ouverte. Ouverte
Difficulté 2/5 1-3 heures Accessibilité débutants 82/100
triggerdotdev/trigger.dev#5083 · 1 commentaire ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 2/5 1-3 heures Accessibilité débutants 83/100
triggerdotdev/trigger.dev#5072 · 1 commentaire ·
Les mainteneurs répondent en général sous 1 jour
Toutes les issues de triggerdotdev/trigger.dev
Issues similaires
-
Difficulté 2/5 1-3 heures Accessibilité débutants 72/100
Les mainteneurs répondent en général sous 1 jour
-
bug platform-android
Difficulté 2/5 1-3 heures Accessibilité débutants 68/100
Termix-SSH/Mobile#146 · 1 commentaire ·
Les mainteneurs répondent en général sous 2 jours
-
bug
Difficulté 2/5 1-3 heures Accessibilité débutants 66/100
devswha/herdr-web-ui#3875 ·
-
Difficulté 1/5 Moins d'une heure Accessibilité débutants 88/100
-
area: runtime chore cli consistency dependencies developer-experience difficulty: easy discovery documentation enhancement good first issue help wanted hygiene json-output packaging priority: P3 tests version
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
Les mainteneurs répondent en général sous 1 jour