Skip to content

Chore: ESM migration #1007

Chore: ESM migration

Chore: ESM migration #1007

Triggered via pull request April 28, 2025 17:01
Status Failure
Total duration 1m 14s
Artifacts

ci.yml

on: pull_request
Matrix: build
automerge
0s
automerge
Fit to window
Zoom out
Zoom in

Annotations

16 errors
build (20.x)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './types.js'?
build (20.x)
Cannot find module '@message-queue-toolkit/core' or its corresponding type declarations.
build (20.x)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './MessageMultiMetricManager.js'?
build (20.x)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './prometheus/types.js'?
build (20.x)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './prometheus/PrometheusMessageMetric.js'?
build (20.x)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './prometheus/metrics/message-error/PrometheusMessageErrorCounter.js'?
build (20.x)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './prometheus/metrics/message-time/PrometheusMessageProcessingTimeMetric.js'?
build (20.x)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './prometheus/metrics/message-time/PrometheusMessageLifetimeMetric.js'?
build (20.x)
This syntax is not allowed when 'erasableSyntaxOnly' is enabled.
build (20.x)
Cannot find module '@message-queue-toolkit/core' or its corresponding type declarations.
build (18.x)
The operation was canceled.
build (18.x)
The strategy configuration was canceled because "build._20_x" failed
build (23.x)
The operation was canceled.
build (23.x)
The strategy configuration was canceled because "build._20_x" failed
build (22.x)
The operation was canceled.
build (22.x)
The strategy configuration was canceled because "build._20_x" failed