# FIXED: TiNG index.html Not Created During Build

**URL:** <https://forum.servoy.com/t/fixed-ting-index-html-not-created-during-build/20938>\
**Category:** Questions\
**Created:** [January 14, 2023, 10:40pm UTC](https://forum.servoy.com/t/fixed-ting-index-html-not-created-during-build/20938 "2023-01-14T22:40:32Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![kwpsd](https://avatars.discourse-cdn.com/v4/letter/k/bb73d2/32.png) [@kwpsd](https://forum.servoy.com/u/kwpsd)\
**Post date:** [January 14, 2023, 10:40pm UTC](https://forum.servoy.com/t/fixed-ting-index-html-not-created-during-build/20938/1 "2023-01-14T22:40:32Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![jcompagner](https://yyz2.discourse-cdn.com/flex010/user_avatar/forum.servoy.com/jcompagner/32/4889_2.png) [@jcompagner](https://forum.servoy.com/u/jcompagner)\
**Post date:** [January 16, 2023, 8:59am UTC](https://forum.servoy.com/t/fixed-ting-index-html-not-created-during-build/20938/2 "2023-01-16T08:59:53Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![kwpsd](https://avatars.discourse-cdn.com/v4/letter/k/bb73d2/32.png) [@kwpsd](https://forum.servoy.com/u/kwpsd)\
**Post date:** [January 16, 2023, 8:06pm UTC](https://forum.servoy.com/t/fixed-ting-index-html-not-created-during-build/20938/3 "2023-01-16T20:06:48Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![kwpsd](https://avatars.discourse-cdn.com/v4/letter/k/bb73d2/32.png) [@kwpsd](https://forum.servoy.com/u/kwpsd)\
**Post date:** [January 17, 2023, 9:30pm UTC](https://forum.servoy.com/t/fixed-ting-index-html-not-created-during-build/20938/4 "2023-01-17T21:30:36Z")

</div>

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](http://registry.npmjs.org) on port 443

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

```auto
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!

---

<div class="post-metadata">

**Author:** ![jcompagner](https://yyz2.discourse-cdn.com/flex010/user_avatar/forum.servoy.com/jcompagner/32/4889_2.png) [@jcompagner](https://forum.servoy.com/u/jcompagner)\
**Post date:** [January 18, 2023, 12:05pm UTC](https://forum.servoy.com/t/fixed-ting-index-html-not-created-during-build/20938/5 "2023-01-18T12:05:32Z")

</div>

> 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.

---

<div class="post-metadata">

**Author:** ![kwpsd](https://avatars.discourse-cdn.com/v4/letter/k/bb73d2/32.png) [@kwpsd](https://forum.servoy.com/u/kwpsd)\
**Post date:** [January 18, 2023, 5:40pm UTC](https://forum.servoy.com/t/fixed-ting-index-html-not-created-during-build/20938/6 "2023-01-18T17:40:34Z")

</div>

Ah, I see…thanks for the better explanation.
