# Help with building Paraview Glance

**URL:** https://discourse.paraview.org/t/help-with-building-paraview-glance/5186
**Category:** Web Support
**Created:** [August 26, 2020, 2:04pm UTC](https://discourse.paraview.org/t/help-with-building-paraview-glance/5186 "2020-08-26T14:04:27Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Ramu](https://discourse.paraview.org/user_avatar/discourse.paraview.org/ramu/32/4773_2.png) [@Ramu](https://discourse.paraview.org/u/Ramu)
#### Post date: [August 26, 2020, 2:04pm UTC](https://discourse.paraview.org/t/help-with-building-paraview-glance/5186/1 "2020-08-26T14:04:27Z")

</div>

Hello I am trying to build paraview-glance from [Kitware](https://github.com/Kitware)/ **[paraview-glance](https://github.com/Kitware/paraview-glance)** GitHub repo. It was successful on my personal laptop but unable to do so in my office machine. (I use enterprise registry and they prevent downloading package from external github)

The issue I found is with `kw-doc` dependency. I get the following error.

```auto
npm ERR! Error while executing:
npm ERR! C:\Program Files\Git\cmd\git.EXE ls-remote -h -t git://github.com/floryst/kw-doc.git
npm ERR!
npm ERR! fatal: read error: Invalid argument
npm ERR!
npm ERR! exited with error code: 128

```

I am planning to download the file and maintain a local copy. But I don’t want to add `kw-doc` in version management. Can anyone suggest an efficient work around ?

Also is the `kw-docs` necessary. I see them in dev dependency. If it is required why can’t it be published to npm ?

---

<div class="post-metadata">

### Author: ![Forrest\_Li](https://discourse.paraview.org/user_avatar/discourse.paraview.org/forrest_li/32/1935_2.png) [@Forrest\_Li](https://discourse.paraview.org/u/Forrest_Li)
#### Post date: [August 26, 2020, 2:19pm UTC](https://discourse.paraview.org/t/help-with-building-paraview-glance/5186/2 "2020-08-26T14:19:45Z")

</div>

Hi, I had used a personal copy of `kw-doc` a while back to fix an issue with website generation via CI, and forgot to move it back to the npm published version. If you change `kw-doc` version in package.json to `1.3.1`, does that work? In the meantime, I will make that change officially as well.
