vercel/ncc

Regression: dynamic runtime `require` works in 0.38.1 but breaks in 0.38.2

Open

#1 312 ouverte le 16 mars 2026

Voir sur GitHub
 (2 commentaires) (0 réactions) (0 assignés)JavaScript (8 841 stars) (273 forks)batch import
help wanted

Description

0.38.1

I have the following source code:

https://github.com/CatChen/eslint-suggestion-action/blob/930479a34a06bfa384291cc877f9d1ce21533ae1/src/getESLint.ts#L16-L19

The dynamic require is compiled into the following code:

https://github.com/CatChen/eslint-suggestion-action/blob/930479a34a06bfa384291cc877f9d1ce21533ae1/bundle/index.js#L37587

0.38.2

The same code is compiled into the following code since 0.38.2:

https://github.com/CatChen/eslint-suggestion-action/blob/bc0de7fa625de9daf56cca84b6084f4d6bcbaca4/bundle/index.js#L37702

Workaround

My current workaround is to use dynamic import inside a new Function() (because dynamic import isn't supported either). I have to change to code into this:

https://github.com/CatChen/eslint-suggestion-action/blob/927208b2e684b1a7c721f4a0e70d4f4e8c11c228/src/getESLint.ts#L15-L26

Guide contributeur

Stack technique
nodejsjavascripttypescript
Domaine
toolingbuild systemdeveloper experience
Type d'issue
bug
DifficultéDifficulté estimée pour un nouveau contributeur, de 1 pour un très petit changement à 5 pour un travail expert.
3
Temps estiméFourchette de temps approximative pour investiguer, implémenter, tester et préparer une pull request.
half day
Statut d'activitéDisponibilité apparente de l'issue : fraîche, active, ancienne, bloquée ou en attente d'un mainteneur.
fresh
ClartéClarté avec laquelle l'issue explique le changement attendu, les critères d'acceptation et la prochaine étape.
needs investigation
Prérequis
basic Node.js module systemfamiliarity with ncc
Accessibilité débutantScore de 1 à 100 estimant l'accessibilité de cette issue pour un premier contributeur.
25
Direction de recherche
Examine the changes between ncc 0.38.1 and 0.38.2, focusing on the bundling logic for dynamic require statements. Look at the generated code differences and identify the commit that introduced the regression. Consider if the issue is related to changes in how require is transformed or if it's a broader problem with dynamic imports. Check the repository's issue tracker for related discussions or pull requests.