Skip to content
CI

fix: loading esm-register via full path from a different cwd #1434

Sign in to view logs

fix: loading esm-register via full path from a different cwd

fix: loading esm-register via full path from a different cwd #1434

Re-run triggered July 7, 2024 14:00
@BrooooooklynBrooooooklyn
#805
ChALkeR:patch-1
Status Failure
Total duration 1m 1s
Artifacts –

CI.yml

on: pull_request
Matrix: test
Publish
0s
Publish
Fit to window
Zoom out
Zoom in

Annotations

6 errors
stable - macos-latest - node@20: packages/register/esm-register.mts#L3
The 'import.meta' meta-property is only allowed when the '--module' option is 'es2020', 'es2022', 'esnext', 'system', 'node16', or 'nodenext'.
stable - macos-latest - node@20
Process completed with exit code 2.
stable - ubuntu-latest - node@20: packages/register/esm-register.mts#L3
The 'import.meta' meta-property is only allowed when the '--module' option is 'es2020', 'es2022', 'esnext', 'system', 'node16', or 'nodenext'.
stable - ubuntu-latest - node@20
Process completed with exit code 2.
stable - windows-latest - node@20: packages/register/esm-register.mts#L3
The 'import.meta' meta-property is only allowed when the '--module' option is 'es2020', 'es2022', 'esnext', 'system', 'node16', or 'nodenext'.
stable - windows-latest - node@20
Process completed with exit code 1.