Skip to content
Build

save #33

Sign in to view logs

save

save #33

Triggered via push January 17, 2024 12:27
@mildronizemildronize
pushed 3a080d4
main.fix-issue-3-4-module-with-tsc
Status Failure
Total duration 22s
Artifacts –

main.yml

on: push
build
14s
build
Fit to window
Zoom out
Zoom in

Annotations

10 errors
build: src/logger.ts#L6
This expression is not callable.
build: src/main.ts#L1
Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
build: src/main.ts#L2
Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Consider adding an extension to the import path.
build: src/view-server/index.ts#L1
Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './server.js'?
build: src/view-server/index.ts#L2
Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './types.js'?
build: src/view-server/index.ts#L3
Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './utils.js'?
build: src/view-server/server.ts#L7
Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './types.js'?
build: src/view-server/server.ts#L9
Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../logger.js'?
build: src/view-server/server.ts#L10
Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './utils.js'?
build
Process completed with exit code 1.