refactor: switch to module
#75
Annotations
21 errors and 1 warning
build (macos-latest):
src/core/ui5ApiBuffer.ts#L1
Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './types.js'?
|
build (macos-latest):
src/core/ui5ApiService.ts#L1
Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './types.js'?
|
build (macos-latest):
src/core/ui5ApiService.ts#L2
Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './constants.js'?
|
build (macos-latest):
src/core/ui5ApiService.ts#L3
Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './dataSource.js'?
|
build (macos-latest):
src/core/ui5ApiService.ts#L4
Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './ui5ApiBuffer.js'?
|
build (macos-latest):
src/core/ui5ApiService.ts#L87
Parameter 'element' implicitly has an 'any' type.
|
build (macos-latest):
src/core/ui5ApiService.ts#L147
Parameter 'element' implicitly has an 'any' type.
|
build (macos-latest):
src/extension.ts#L2
Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './view/ApiReferenceProvider.js'?
|
build (macos-latest):
src/extension.ts#L3
Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './core/ui5ApiService.js'?
|
build (macos-latest):
src/extension.ts#L4
Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './core/dataSource.js'?
|
build (ubuntu-latest)
The job was canceled because "macos-latest" failed.
|
build (ubuntu-latest):
src/core/ui5ApiBuffer.ts#L1
Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './types.js'?
|
build (ubuntu-latest):
src/core/ui5ApiService.ts#L1
Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './types.js'?
|
build (ubuntu-latest):
src/core/ui5ApiService.ts#L2
Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './constants.js'?
|
build (ubuntu-latest):
src/core/ui5ApiService.ts#L3
Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './dataSource.js'?
|
build (ubuntu-latest):
src/core/ui5ApiService.ts#L4
Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './ui5ApiBuffer.js'?
|
build (ubuntu-latest):
src/core/ui5ApiService.ts#L87
Parameter 'element' implicitly has an 'any' type.
|
build (ubuntu-latest):
src/core/ui5ApiService.ts#L147
Parameter 'element' implicitly has an 'any' type.
|
build (ubuntu-latest):
src/extension.ts#L2
Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './view/ApiReferenceProvider.js'?
|
build (ubuntu-latest):
src/extension.ts#L3
Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './core/ui5ApiService.js'?
|
build (ubuntu-latest):
src/extension.ts#L4
Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './core/dataSource.js'?
|
build (macos-latest)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|