ui5 use error expecting manifest.json to already be present
See original GitHub issueHi all
I’m having on issue with this on Windows 10, using Powershell or CMD. It won’t set up a ui5 project for me, always fails with the following error, as it seems to expect a manifest.json already (which it’s supposed to set up):
Error Message: Failed to read manifest.json for project ui5-test: ENOENT: no such file or directory, open ‘C:\Users\USER\git\ui5-test\webapp\manifest.json’
Expected Behavior
set up an initial UI5 project by using ui5 init and ui5 use openui5@latest
Current Behavior
ui5 init fails with the message:
Error Message: Could not detect project type: Could not find ‘webapp’ or ‘src’ / ‘test’ folders. Applications should only have a ‘webapp’ folder. Libraries should only have a ‘src’ and (optional) ‘test’ folder.
If I create the folder “webapp” manually, then run ui5 use openui5@latest, I get the error
Error Message: Failed to read manifest.json for project ui5-test: ENOENT: no such file or directory, open ‘C:\Users\USER\git\ui5-test\webapp\manifest.json’
Steps to reproduce the issue
- mkdir ui5-test
- cd ui5-test
- npm init -y
- ui5 init
- mkdir webapp
- ui5 use openui5@latest OR ui5 use sapui5@latest
Context
- UI5 Module Version (output of
ui5 --version
when using the CLI):2.0.2
- Node.js Version:
v12.13.1
- npm Version:
6.14.4
- OS/Platform:
Windows 10
- Browser (if relevant):
{...}
- Other information:
Powershell 7 or CMD
Affected components (if known)
Log Output / Stack Trace
{...}
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Hi
thank you for the reply - I’ve since also come to this conclusion, apparently projects should be initialised in the WebIDE first and then downloaded to the local environment. In my opinion this limits access for people who don’t have access to the WebIDE. While scaffolding would be nice, I understand that it takes time, so in the meantime maybe you could provide additional documentation about the manual steps we need to take to get this to work, i.e. what directories need to be created and a minimal manifest.json file that’s required. That way it could still be used locally, albeit with some additional setup.
Thank you Akos
Hey, sorry for the late reply.
Apparently this works as designed. We always need the projects namespace information, which is located in the manifest.json.
In the future, project setup should become easier with the use of scaffolding. Until then we should definitely improve this error message. Thanks for reporting!