When UI5 types are not recognized, one reason could be that the UI5 type definitions are not available - an error message is hinting at this is already given. It could be more verbose, though, and:
inform the user at which paths the type definitions are expected to be according to tsconfig
check these locations whether the definitions are there
if not, hint to reasons why this could be the case (npm install missing or installed in a different node_modules folder)
possibly even check the hierarchy for such node_modules folders and look whether the types are there
When UI5 types are not recognized, one reason could be that the UI5 type definitions are not available - an error message is hinting at this is already given. It could be more verbose, though, and:
As reported in https://github.com/ui5-community/generator-ui5-ts-library/issues/2, it can happen that due to some yarn setup the types are installed somewhere else.