FIXED: TiNG index.html Not Created During Build

Questions
1

Servoy TiNG Version: 2022.9.2.3805

I create a new workspace and import a solution. Developer goes through the process of building the solution but ultimately fails with the following console message:

‘ng’ is not recognized as an internal or external command

Developer shows the following information:

Message The requested resource [/solution/ARMTITAN/index.html] is not available

Description The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.

I verified that the index.html files does not exist in the following path:

C:\Users.…\servoy_workspace.metadata.plugins\com.servoy.eclipse.ngclient.ui\target\ARMTITAN

No errors in servoy_log.txt or in the .metadata .log file.

Any ideas as to what would prevent the index.html from being created and why ‘ng’ is not recognized as a valid command? …and, why there are no errors reported?

2

then something is really not installed correctly in the dir.
Not sure why that sometimes just doesn’t work for some.

What you can do is in the context menu of the Web Packages → copy titanium ng resources and then choose for the “clean” option

“ng” should just be there, that should be installed. that is “angular/cli” npm package.

so i do wonder if nothing before that in the log goes wrong, but for that we have to see the full log of the Titanium NG Build Console

3

Johan…the log files were sent to your e-mail account.

4

Posting the information below for others who may be having this issue.

Johan,

Not sure why that sometimes just doesn’t work for some.

I figured out why the index.html file is not being created.

Apparently, during the build process, npm is attempting to connect to some Angular server, and if the connection fails, the index.html file is not created resulting in the following message:

‘ng’ is not recognized as an internal or external command

In our case, our network firewall was preventing the connection. npm was attempting to connect to:

registry.npmjs.org on port 443

If you look up the IP address for this domain, you will get the following:

104.16.16.35
104.16.17.35
104.16.18.35
104.16.19.35
104.16.20.35
104.16.21.35
104.16.22.35
104.16.23.35
104.16.24.35
104.16.25.35
104.16.26.35
104.16.27.35

We allowed these IP addresses through our firewall, and npm would then run to completion.

I hope this helps!

5

kwpsd:
Apparently, during the build process, npm is attempting to connect to some Angular server, and if the connection fails, the index.html file is not created resulting in the following message:

no it is not the an angular server that we want to connect to
but just to the npm registry to get all the npm packages, not just angular but a lot of other packages like the stuff we build on top of (datepicker, bootstrap, fontawesome)

and yes for TiNG that is very important that that works, those downloads should not be blocked.

6

Ah, I see…thanks for the better explanation.