Migrate the runtime to esm #5838
jkoenig134test.yml
on: pull_request
run-checks
1m 2s
test-app-runtime
1m 45s
test-consumption-mongodb
1m 55s
test-consumption-loki
1m 38s
test-content
1m 5s
test-core-types
1m 5s
test-runtime-mongodb
1m 58s
test-runtime-loki
1m 35s
test-transport-mongodb
1m 51s
test-transport-loki
1m 39s
Annotations
91 errors
|
run-checks
Process completed with exit code 2.
|
|
test-core-types:
packages/consumption/src/index.ts#L6
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionCoreErrors.js'?
|
|
test-core-types:
packages/consumption/src/index.ts#L5
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionControllerName.js'?
|
|
test-core-types:
packages/consumption/src/index.ts#L4
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionController.js'?
|
|
test-core-types:
packages/consumption/src/index.ts#L3
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionConfig.js'?
|
|
test-core-types:
packages/consumption/src/index.ts#L2
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionBaseController.js'?
|
|
test-core-types:
packages/consumption/src/index.ts#L1
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './buildInformation.js'?
|
|
test-core-types:
packages/consumption/src/consumption/ConsumptionController.ts#L45
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './ConsumptionConfig.js'?
|
|
test-core-types:
packages/consumption/src/consumption/ConsumptionController.ts#L44
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
|
|
test-core-types:
packages/consumption/src/consumption/ConsumptionBaseController.ts#L5
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './ConsumptionControllerName.js'?
|
|
test-core-types:
packages/consumption/src/consumption/ConsumptionBaseController.ts#L4
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './ConsumptionController.js'?
|
|
test-content:
packages/consumption/src/index.ts#L6
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionCoreErrors.js'?
|
|
test-content:
packages/consumption/src/index.ts#L5
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionControllerName.js'?
|
|
test-content:
packages/consumption/src/index.ts#L4
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionController.js'?
|
|
test-content:
packages/consumption/src/index.ts#L3
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionConfig.js'?
|
|
test-content:
packages/consumption/src/index.ts#L2
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionBaseController.js'?
|
|
test-content:
packages/consumption/src/index.ts#L1
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './buildInformation.js'?
|
|
test-content:
packages/consumption/src/consumption/ConsumptionController.ts#L45
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './ConsumptionConfig.js'?
|
|
test-content:
packages/consumption/src/consumption/ConsumptionController.ts#L44
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
|
|
test-content:
packages/consumption/src/consumption/ConsumptionBaseController.ts#L5
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './ConsumptionControllerName.js'?
|
|
test-content:
packages/consumption/src/consumption/ConsumptionBaseController.ts#L4
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './ConsumptionController.js'?
|
|
test-runtime-loki:
packages/consumption/src/index.ts#L6
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionCoreErrors.js'?
|
|
test-runtime-loki:
packages/consumption/src/index.ts#L5
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionControllerName.js'?
|
|
test-runtime-loki:
packages/consumption/src/index.ts#L4
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionController.js'?
|
|
test-runtime-loki:
packages/consumption/src/index.ts#L3
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionConfig.js'?
|
|
test-runtime-loki:
packages/consumption/src/index.ts#L2
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionBaseController.js'?
|
|
test-runtime-loki:
packages/consumption/src/index.ts#L1
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './buildInformation.js'?
|
|
test-runtime-loki:
packages/consumption/src/consumption/ConsumptionController.ts#L45
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './ConsumptionConfig.js'?
|
|
test-runtime-loki:
packages/consumption/src/consumption/ConsumptionController.ts#L44
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
|
|
test-runtime-loki:
packages/consumption/src/consumption/ConsumptionBaseController.ts#L5
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './ConsumptionControllerName.js'?
|
|
test-runtime-loki:
packages/consumption/src/consumption/ConsumptionBaseController.ts#L4
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './ConsumptionController.js'?
|
|
test-consumption-loki:
packages/consumption/src/index.ts#L6
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionCoreErrors.js'?
|
|
test-consumption-loki:
packages/consumption/src/index.ts#L5
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionControllerName.js'?
|
|
test-consumption-loki:
packages/consumption/src/index.ts#L4
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionController.js'?
|
|
test-consumption-loki:
packages/consumption/src/index.ts#L3
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionConfig.js'?
|
|
test-consumption-loki:
packages/consumption/src/index.ts#L2
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionBaseController.js'?
|
|
test-consumption-loki:
packages/consumption/src/index.ts#L1
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './buildInformation.js'?
|
|
test-consumption-loki:
packages/consumption/src/consumption/ConsumptionController.ts#L45
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './ConsumptionConfig.js'?
|
|
test-consumption-loki:
packages/consumption/src/consumption/ConsumptionController.ts#L44
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
|
|
test-consumption-loki:
packages/consumption/src/consumption/ConsumptionBaseController.ts#L5
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './ConsumptionControllerName.js'?
|
|
test-consumption-loki:
packages/consumption/src/consumption/ConsumptionBaseController.ts#L4
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './ConsumptionController.js'?
|
|
test-transport-loki:
packages/consumption/src/index.ts#L6
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionCoreErrors.js'?
|
|
test-transport-loki:
packages/consumption/src/index.ts#L5
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionControllerName.js'?
|
|
test-transport-loki:
packages/consumption/src/index.ts#L4
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionController.js'?
|
|
test-transport-loki:
packages/consumption/src/index.ts#L3
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionConfig.js'?
|
|
test-transport-loki:
packages/consumption/src/index.ts#L2
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionBaseController.js'?
|
|
test-transport-loki:
packages/consumption/src/index.ts#L1
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './buildInformation.js'?
|
|
test-transport-loki:
packages/consumption/src/consumption/ConsumptionController.ts#L45
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './ConsumptionConfig.js'?
|
|
test-transport-loki:
packages/consumption/src/consumption/ConsumptionController.ts#L44
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
|
|
test-transport-loki:
packages/consumption/src/consumption/ConsumptionBaseController.ts#L5
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './ConsumptionControllerName.js'?
|
|
test-transport-loki:
packages/consumption/src/consumption/ConsumptionBaseController.ts#L4
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './ConsumptionController.js'?
|
|
test-app-runtime:
packages/consumption/src/index.ts#L6
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionCoreErrors.js'?
|
|
test-app-runtime:
packages/consumption/src/index.ts#L5
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionControllerName.js'?
|
|
test-app-runtime:
packages/consumption/src/index.ts#L4
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionController.js'?
|
|
test-app-runtime:
packages/consumption/src/index.ts#L3
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionConfig.js'?
|
|
test-app-runtime:
packages/consumption/src/index.ts#L2
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionBaseController.js'?
|
|
test-app-runtime:
packages/consumption/src/index.ts#L1
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './buildInformation.js'?
|
|
test-app-runtime:
packages/consumption/src/consumption/ConsumptionController.ts#L45
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './ConsumptionConfig.js'?
|
|
test-app-runtime:
packages/consumption/src/consumption/ConsumptionController.ts#L44
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
|
|
test-app-runtime:
packages/consumption/src/consumption/ConsumptionBaseController.ts#L5
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './ConsumptionControllerName.js'?
|
|
test-app-runtime:
packages/consumption/src/consumption/ConsumptionBaseController.ts#L4
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './ConsumptionController.js'?
|
|
test-transport-mongodb:
packages/consumption/src/index.ts#L6
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionCoreErrors.js'?
|
|
test-transport-mongodb:
packages/consumption/src/index.ts#L5
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionControllerName.js'?
|
|
test-transport-mongodb:
packages/consumption/src/index.ts#L4
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionController.js'?
|
|
test-transport-mongodb:
packages/consumption/src/index.ts#L3
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionConfig.js'?
|
|
test-transport-mongodb:
packages/consumption/src/index.ts#L2
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionBaseController.js'?
|
|
test-transport-mongodb:
packages/consumption/src/index.ts#L1
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './buildInformation.js'?
|
|
test-transport-mongodb:
packages/consumption/src/consumption/ConsumptionController.ts#L45
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './ConsumptionConfig.js'?
|
|
test-transport-mongodb:
packages/consumption/src/consumption/ConsumptionController.ts#L44
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
|
|
test-transport-mongodb:
packages/consumption/src/consumption/ConsumptionBaseController.ts#L5
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './ConsumptionControllerName.js'?
|
|
test-transport-mongodb:
packages/consumption/src/consumption/ConsumptionBaseController.ts#L4
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './ConsumptionController.js'?
|
|
test-consumption-mongodb:
packages/consumption/src/index.ts#L6
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionCoreErrors.js'?
|
|
test-consumption-mongodb:
packages/consumption/src/index.ts#L5
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionControllerName.js'?
|
|
test-consumption-mongodb:
packages/consumption/src/index.ts#L4
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionController.js'?
|
|
test-consumption-mongodb:
packages/consumption/src/index.ts#L3
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionConfig.js'?
|
|
test-consumption-mongodb:
packages/consumption/src/index.ts#L2
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionBaseController.js'?
|
|
test-consumption-mongodb:
packages/consumption/src/index.ts#L1
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './buildInformation.js'?
|
|
test-consumption-mongodb:
packages/consumption/src/consumption/ConsumptionController.ts#L45
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './ConsumptionConfig.js'?
|
|
test-consumption-mongodb:
packages/consumption/src/consumption/ConsumptionController.ts#L44
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
|
|
test-consumption-mongodb:
packages/consumption/src/consumption/ConsumptionBaseController.ts#L5
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './ConsumptionControllerName.js'?
|
|
test-consumption-mongodb:
packages/consumption/src/consumption/ConsumptionBaseController.ts#L4
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './ConsumptionController.js'?
|
|
test-runtime-mongodb:
packages/consumption/src/index.ts#L6
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionCoreErrors.js'?
|
|
test-runtime-mongodb:
packages/consumption/src/index.ts#L5
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionControllerName.js'?
|
|
test-runtime-mongodb:
packages/consumption/src/index.ts#L4
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionController.js'?
|
|
test-runtime-mongodb:
packages/consumption/src/index.ts#L3
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionConfig.js'?
|
|
test-runtime-mongodb:
packages/consumption/src/index.ts#L2
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './consumption/ConsumptionBaseController.js'?
|
|
test-runtime-mongodb:
packages/consumption/src/index.ts#L1
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './buildInformation.js'?
|
|
test-runtime-mongodb:
packages/consumption/src/consumption/ConsumptionController.ts#L45
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './ConsumptionConfig.js'?
|
|
test-runtime-mongodb:
packages/consumption/src/consumption/ConsumptionController.ts#L44
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
|
|
test-runtime-mongodb:
packages/consumption/src/consumption/ConsumptionBaseController.ts#L5
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './ConsumptionControllerName.js'?
|
|
test-runtime-mongodb:
packages/consumption/src/consumption/ConsumptionBaseController.ts#L4
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './ConsumptionController.js'?
|