fix postintall 3 #368
Annotations
61 errors and 10 warnings
main (ubuntu-latest, 1.90.2, stable):
src/commands/AbstractNewCamelRouteCommand.ts#L21
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './AbstractCamelCommand.js'?
|
main (ubuntu-latest, 1.90.2, stable):
src/commands/AbstractNewCamelRouteCommand.ts#L31
Property 'camelDSL' does not exist on type 'AbstractNewCamelRouteCommand'.
|
main (ubuntu-latest, 1.90.2, stable):
src/commands/AbstractNewCamelRouteCommand.ts#L33
Property 'validateCamelFileName' does not exist on type 'AbstractNewCamelRouteCommand'.
|
main (ubuntu-latest, 1.90.2, stable):
src/commands/AbstractTransformCamelRouteCommand.ts#L20
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './AbstractCamelCommand.js'?
|
main (ubuntu-latest, 1.90.2, stable):
src/commands/NewCamelFileCommand.ts#L20
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './NewCamelRouteCommand.js'?
|
main (ubuntu-latest, 1.90.2, stable):
src/commands/NewCamelFileCommand.ts#L21
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './NewCamelRouteFromOpenAPICommand.js'?
|
main (ubuntu-latest, 1.90.2, stable):
src/commands/NewCamelFileCommand.ts#L22
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './NewCamelKameletCommand.js'?
|
main (ubuntu-latest, 1.90.2, stable):
src/commands/NewCamelFileCommand.ts#L23
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './NewCamelPipeCommand.js'?
|
main (ubuntu-latest, 1.90.2, stable):
src/commands/NewCamelKameletCommand.ts#L20
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './AbstractNewCamelRouteCommand.js'?
|
main (ubuntu-latest, 1.90.2, stable):
src/commands/NewCamelKameletCommand.ts#L21
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../tasks/CamelInitJBangTask.js'?
|
main (ubuntu-latest, max, stable):
src/commands/AbstractNewCamelRouteCommand.ts#L21
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './AbstractCamelCommand.js'?
|
main (ubuntu-latest, max, stable):
src/commands/AbstractNewCamelRouteCommand.ts#L31
Property 'camelDSL' does not exist on type 'AbstractNewCamelRouteCommand'.
|
main (ubuntu-latest, max, stable):
src/commands/AbstractNewCamelRouteCommand.ts#L33
Property 'validateCamelFileName' does not exist on type 'AbstractNewCamelRouteCommand'.
|
main (ubuntu-latest, max, stable):
src/commands/AbstractTransformCamelRouteCommand.ts#L20
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './AbstractCamelCommand.js'?
|
main (ubuntu-latest, max, stable):
src/commands/NewCamelFileCommand.ts#L20
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './NewCamelRouteCommand.js'?
|
main (ubuntu-latest, max, stable):
src/commands/NewCamelFileCommand.ts#L21
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './NewCamelRouteFromOpenAPICommand.js'?
|
main (ubuntu-latest, max, stable):
src/commands/NewCamelFileCommand.ts#L22
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './NewCamelKameletCommand.js'?
|
main (ubuntu-latest, max, stable):
src/commands/NewCamelFileCommand.ts#L23
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './NewCamelPipeCommand.js'?
|
main (ubuntu-latest, max, stable):
src/commands/NewCamelKameletCommand.ts#L20
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './AbstractNewCamelRouteCommand.js'?
|
main (ubuntu-latest, max, stable):
src/commands/NewCamelKameletCommand.ts#L21
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../tasks/CamelInitJBangTask.js'?
|
main (macos-latest, max, stable):
src/commands/AbstractNewCamelRouteCommand.ts#L21
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './AbstractCamelCommand.js'?
|
main (macos-latest, max, stable):
src/commands/AbstractNewCamelRouteCommand.ts#L31
Property 'camelDSL' does not exist on type 'AbstractNewCamelRouteCommand'.
|
main (macos-latest, max, stable):
src/commands/AbstractNewCamelRouteCommand.ts#L33
Property 'validateCamelFileName' does not exist on type 'AbstractNewCamelRouteCommand'.
|
main (macos-latest, max, stable):
src/commands/AbstractTransformCamelRouteCommand.ts#L20
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './AbstractCamelCommand.js'?
|
main (macos-latest, max, stable):
src/commands/NewCamelFileCommand.ts#L20
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './NewCamelRouteCommand.js'?
|
main (macos-latest, max, stable):
src/commands/NewCamelFileCommand.ts#L21
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './NewCamelRouteFromOpenAPICommand.js'?
|
main (macos-latest, max, stable):
src/commands/NewCamelFileCommand.ts#L22
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './NewCamelKameletCommand.js'?
|
main (macos-latest, max, stable):
src/commands/NewCamelFileCommand.ts#L23
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './NewCamelPipeCommand.js'?
|
main (macos-latest, max, stable):
src/commands/NewCamelKameletCommand.ts#L20
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './AbstractNewCamelRouteCommand.js'?
|
main (macos-latest, max, stable):
src/commands/NewCamelKameletCommand.ts#L21
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../tasks/CamelInitJBangTask.js'?
|
main (macos-latest, 1.90.2, stable):
src/commands/AbstractNewCamelRouteCommand.ts#L21
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './AbstractCamelCommand.js'?
|
main (macos-latest, 1.90.2, stable):
src/commands/AbstractNewCamelRouteCommand.ts#L31
Property 'camelDSL' does not exist on type 'AbstractNewCamelRouteCommand'.
|
main (macos-latest, 1.90.2, stable):
src/commands/AbstractNewCamelRouteCommand.ts#L33
Property 'validateCamelFileName' does not exist on type 'AbstractNewCamelRouteCommand'.
|
main (macos-latest, 1.90.2, stable):
src/commands/AbstractTransformCamelRouteCommand.ts#L20
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './AbstractCamelCommand.js'?
|
main (macos-latest, 1.90.2, stable):
src/commands/NewCamelFileCommand.ts#L20
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './NewCamelRouteCommand.js'?
|
main (macos-latest, 1.90.2, stable):
src/commands/NewCamelFileCommand.ts#L21
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './NewCamelRouteFromOpenAPICommand.js'?
|
main (macos-latest, 1.90.2, stable):
src/commands/NewCamelFileCommand.ts#L22
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './NewCamelKameletCommand.js'?
|
main (macos-latest, 1.90.2, stable):
src/commands/NewCamelFileCommand.ts#L23
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './NewCamelPipeCommand.js'?
|
main (macos-latest, 1.90.2, stable):
src/commands/NewCamelKameletCommand.ts#L20
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './AbstractNewCamelRouteCommand.js'?
|
main (macos-latest, 1.90.2, stable):
src/commands/NewCamelKameletCommand.ts#L21
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../tasks/CamelInitJBangTask.js'?
|
main (windows-latest, 1.90.2, stable):
src/commands/AbstractNewCamelRouteCommand.ts#L21
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './AbstractCamelCommand.js'?
|
main (windows-latest, 1.90.2, stable):
src/commands/AbstractNewCamelRouteCommand.ts#L31
Property 'camelDSL' does not exist on type 'AbstractNewCamelRouteCommand'.
|
main (windows-latest, 1.90.2, stable):
src/commands/AbstractNewCamelRouteCommand.ts#L33
Property 'validateCamelFileName' does not exist on type 'AbstractNewCamelRouteCommand'.
|
main (windows-latest, 1.90.2, stable):
src/commands/AbstractTransformCamelRouteCommand.ts#L20
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './AbstractCamelCommand.js'?
|
main (windows-latest, 1.90.2, stable):
src/commands/NewCamelFileCommand.ts#L20
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './NewCamelRouteCommand.js'?
|
main (windows-latest, 1.90.2, stable):
src/commands/NewCamelFileCommand.ts#L21
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './NewCamelRouteFromOpenAPICommand.js'?
|
main (windows-latest, 1.90.2, stable):
src/commands/NewCamelFileCommand.ts#L22
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './NewCamelKameletCommand.js'?
|
main (windows-latest, 1.90.2, stable):
src/commands/NewCamelFileCommand.ts#L23
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './NewCamelPipeCommand.js'?
|
main (windows-latest, 1.90.2, stable):
src/commands/NewCamelKameletCommand.ts#L20
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './AbstractNewCamelRouteCommand.js'?
|
main (windows-latest, 1.90.2, stable):
src/commands/NewCamelKameletCommand.ts#L21
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../tasks/CamelInitJBangTask.js'?
|
main (windows-latest, max, stable):
src/commands/AbstractNewCamelRouteCommand.ts#L21
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './AbstractCamelCommand.js'?
|
main (windows-latest, max, stable):
src/commands/AbstractNewCamelRouteCommand.ts#L31
Property 'camelDSL' does not exist on type 'AbstractNewCamelRouteCommand'.
|
main (windows-latest, max, stable):
src/commands/AbstractNewCamelRouteCommand.ts#L33
Property 'validateCamelFileName' does not exist on type 'AbstractNewCamelRouteCommand'.
|
main (windows-latest, max, stable):
src/commands/AbstractTransformCamelRouteCommand.ts#L20
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './AbstractCamelCommand.js'?
|
main (windows-latest, max, stable):
src/commands/NewCamelFileCommand.ts#L20
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './NewCamelRouteCommand.js'?
|
main (windows-latest, max, stable):
src/commands/NewCamelFileCommand.ts#L21
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './NewCamelRouteFromOpenAPICommand.js'?
|
main (windows-latest, max, stable):
src/commands/NewCamelFileCommand.ts#L22
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './NewCamelKameletCommand.js'?
|
main (windows-latest, max, stable):
src/commands/NewCamelFileCommand.ts#L23
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './NewCamelPipeCommand.js'?
|
main (windows-latest, max, stable):
src/commands/NewCamelKameletCommand.ts#L20
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './AbstractNewCamelRouteCommand.js'?
|
main (windows-latest, max, stable):
src/commands/NewCamelKameletCommand.ts#L21
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean '../tasks/CamelInitJBangTask.js'?
|
Status Check
Process completed with exit code 1.
|
main (ubuntu-latest, 1.90.2, stable)
No files were found with the provided path: /tmp/log-camel-lsp.log
/tmp/log-camel*.log.gz. No artifacts will be uploaded.
|
main (ubuntu-latest, 1.90.2, stable)
No files were found with the provided path: .vscode-test/logs/*. No artifacts will be uploaded.
|
main (ubuntu-latest, max, stable)
No files were found with the provided path: /tmp/log-camel-lsp.log
/tmp/log-camel*.log.gz. No artifacts will be uploaded.
|
main (ubuntu-latest, max, stable)
No files were found with the provided path: .vscode-test/logs/*. No artifacts will be uploaded.
|
main (macos-latest, max, stable)
No files were found with the provided path: .vscode-test/logs/*. No artifacts will be uploaded.
|
main (macos-latest, max, stable)
No files were found with the provided path: /tmp/log-camel-lsp.log
/tmp/log-camel*.log.gz. No artifacts will be uploaded.
|
main (macos-latest, 1.90.2, stable)
No files were found with the provided path: /tmp/log-camel-lsp.log
/tmp/log-camel*.log.gz. No artifacts will be uploaded.
|
main (macos-latest, 1.90.2, stable)
No files were found with the provided path: .vscode-test/logs/*. No artifacts will be uploaded.
|
main (windows-latest, 1.90.2, stable)
No files were found with the provided path: .vscode-test/logs/*. No artifacts will be uploaded.
|
main (windows-latest, max, stable)
No files were found with the provided path: .vscode-test/logs/*. No artifacts will be uploaded.
|