Skip to content

Replace yarn nodeLinker pnpm node by node-modules #224

Replace yarn nodeLinker pnpm node by node-modules

Replace yarn nodeLinker pnpm node by node-modules #224

Triggered via pull request January 8, 2025 11:05
Status Failure
Total duration 1m 54s
Artifacts

pull-request.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 1 warning
build (20.x)
Cannot find module 'lodash/fp' 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 './HousingFiltersDTO.js'?
build (20.x)
Cannot find module 'lodash/fp' 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 './Occupancy.js'?
build (20.x)
Parameter 'occupancy' implicitly has an 'any' type.
build (20.x)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './FileUploadDTO.js'?
build (20.x)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './SenderDTO.js'?
build (20.x)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './HousingDTO.js'?
build (20.x)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './OwnerDTO.js'?
build (20.x)
Relative import paths need explicit file extensions in ECMAScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './EstablishmentKind.js'?
build (20.x)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636