Skip to content

esm: add import trace for evaluation errors #82934

esm: add import trace for evaluation errors

esm: add import trace for evaluation errors #82934

Re-run triggered February 1, 2026 16:25
Status Failure
Total duration 4m 27s
Artifacts

linters.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

10 errors
lint-js-and-md: lib/internal/modules/esm/module_job.js#L69
Expected { after 'if' condition
lint-js-and-md: lib/internal/modules/esm/module_job.js#L69
Expected indentation of 2 spaces but found 3
lint-js-and-md: lib/internal/modules/esm/module_job.js#L65
Non-ASCII character '’' detected. Consider replacing with: '
lint-js-and-md: lib/internal/modules/esm/module_job.js#L55
Missing JSDoc @returns declaration
lint-js-and-md: lib/internal/modules/esm/module_job.js#L45
Expected { after 'if' condition
lint-js-and-md: lib/internal/modules/esm/module_job.js#L41
Use `const { SafeSet } = primordials;` instead of the global
lint-js-and-md: lib/internal/modules/esm/module_job.js#L34
Missing JSDoc @returns declaration
lint-js-and-md: lib/internal/modules/esm/module_job.js#L29
Use destructuring to define error codes used in the file
lint-js-and-md: lib/internal/modules/esm/module_job.js#L28
Out of ASCIIbetical order - overrideStackTrace >= ErrorPrepareStackTrace
lint-js-and-md: lib/internal/modules/esm/loader.js#L214
Use `const { SafeMap } = primordials;` instead of the global