You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Workaround: make it impossible to analyse import by using expression rather than a literal inside dynamic import statement. For example: import('i' + 'mport-meta-resolve').
Logs
No response
The text was updated successfully, but these errors were encountered:
Thanks for nice reproduction @brawaru. I have narrowed it down to a specific option of jiti. It only happens when require cache is disabled and we do disable it for jitiOptions in c12 by default in order to support invalidating config reloads.
Environment
Package: c12@1.1.2.
Node: v16.14.2, v18.14.0.
Reproduction
import-meta-resolve
.Describe the bug
JITI gets stuck in recursion until eventually it crashes with ‘Maximum call stack size exceeded’.
Additional context
StackBlitz: https://stackblitz.com/edit/node-fughmd?file=example.config.mjs&view=editor.
This is not reproduceable with JITI alone.
Workaround: make it impossible to analyse import by using expression rather than a literal inside dynamic import statement. For example:
import('i' + 'mport-meta-resolve')
.Logs
No response
The text was updated successfully, but these errors were encountered: