SAP-samples/ui5-typescript-tutorial

manifest.json not found

allanvigiano opened this issue · 1 comments

allanvigiano commented

Hi! I followed the whole tutorial and it was awesome! Thanks!

The only problem I faced was the GET manifest.json which is return with a 404 Not Found. The Chrome console shows this message:

It's not needed to call IconPool.insertFontFaceStyle to insert font-face for the predefined icon font SAP-icons because the font-face is included in the library.css of sap.ui.core -

The files not found were:

My package.json is:

{
	"name": "com.myorg.myapp",
	"version": "1.0.0",
	"description": "UI5 Application: com.myorg.myapp",
	"license": "Apache-2.0",
	"scripts": {
		"clean": "rimraf dist coverage",
		"build": "ui5 build --clean-dest",
		"build:opt": "ui5 build self-contained --clean-dest --all",
		"start": "ui5 serve --port 8080 -o index.html",
		"start-cdn": "ui5 serve --port 8080 -o index-cdn.html",
		"start:dist": "npm start -- --config ui5-dist.yaml",
		"start:dist-cdn": "npm run start-cdn -- --config ui5-dist.yaml",
		"ts-typecheck": "tsc --noEmit",
		"lint": "eslint webapp",
		"karma": "karma start",
		"karma-ci": "karma start karma-ci.conf.js",
		"karma-ci-cov": "karma start karma-ci-cov.conf.js",
		"test": "npm run lint && npm run karma-ci-cov"
	},
	"devDependencies": {
		"@sapui5/types": "1.117.0",
		"@typescript-eslint/eslint-plugin": "^5.61.0",
		"@typescript-eslint/parser": "^5.61.0",
		"@ui5/cli": "^3.3.1",
		"@ui5/ts-interface-generator": "^0.7.0",
		"eslint": "^8.44.0",
		"karma": "^6.4.2",
		"karma-chrome-launcher": "^3.2.0",
		"karma-coverage": "^2.2.1",
		"karma-ui5": "^3.0.3",
		"karma-ui5-transpile": "^0.3.22",
		"nominatim-client": "^3.2.1",
		"rimraf": "^5.0.1",
		"typescript": "^5.1.6",
		"ui5-middleware-livereload": "^0.8.4",
		"ui5-tooling-modules": "^3.0.4",
		"ui5-tooling-transpile": "^0.7.17"
	}
}

NPM version: 9.6.7
Node.js version: 18.17.0
On creating the project I consciously selected the "UI5" rather than "OpenUI5" which I think is irrelevant.
Could you help me?

UPDATES:

1 - I figured it out that the problem happens only through npm run start. Running npm run start:dist after build the project everything went wright, all manifest.json could be reached by GET. The problem is probably related to the UI5 dev server. I'm scouring the internet but no success yet.

akudev commented

This is not a bug and does not cause a problem. As you figured out, this is related to the UI5 dev server using the unbuilt UI5 sources by default. The manifest.json is generated when doing npm run build:opt, which in turn does a ui5 build --all (also builds UI5 itself) and among other messages shows this line in the console:

info sap.m › Running task generateLibraryManifest...

So this is not an issue and also not related to the tutorial, but generally happening.