Error with node and/or Angular

[waynevillars]

I tried following the instructions to install navigator via Docker on an Ubuntu EC2 instance, but something involving node and/or angular failed. I apologize for lack of detail, but I know nothing about either one of those things. I've attached a terminal transcript so you can see the errors, as well as a screenshot of what I see when I try to browse to the navigator.

attack navigator install failure log.txt

[beerMT]

Bumping - getting the same issue doing the docker install.

Numerous *Module errors are reported and then StdOut shows - ** Angular Live Development Server is listening on 0.0.0.0:4200, open your browser on http://localhost:4200/ **

When you navigate to localhost:4200 it has the error as shown in the screen shot above. Port (-p) passed to container on startup is the same.

[isaisabel]

Hi all,

We've observed a similar (or possibly parallel) issue when building the Navigator outside of docker, but with outdated versions of Angular installed (we upgraded Angular from v7 to v11 in the v4.1 release). The solution in that case is to remove node_modules and reinstall to ensure the correct version of Angular is installed.

Have either of you used the Navigator through docker previously? I'm wondering if a previous install may be affecting the new build.

[waynevillars]

Yes, we had previously built Navigator through docker and it worked fine. We were trying to upgrade, which is what brought this all about. We initially tried to just build a new Navigator docker image on the original machine. When that failed, we thought the same thing as you (that a previous installation was causing problems), so we blew the old machine away (meaning the entire VM/EC2 instance) and started with a new one, but we ran into the same issue.

[isaisabel]

Good to know, thanks. We are prioritizing #254/#251 since that affects the live instance, but we'll look into this afterwards.

[jberry777]

I haven't updated since December 15th 2020. That dockerized Navigator is still operational.
However, today I tried to build Navigator locally through docker to test new layers and encountered the same errors as described in the initial post. The first error prompted me to update to the newest npm version (7.3.0 -> 7.4.1) but when rebuilding I encountered the same errors.

[isaisabel]

Hi all,

This issue has been addressed in #257 and docker is now working on the develop branch. We'll be releasing Navigator v4.2 (which includes this fix) later this week, but you're welcome to use the develop branch until then if desired.