[BUG] frontend build fails

[nicokant]

Describe the bug
frontend build fails, this happens also using docker-compose build

To Reproduce
Steps to reproduce the behavior:

1. clone the repository
2. cd frontend && npm install
3. npm run build

Build fails with error:

> TaskingManager-frontend@0.1.0 build /home/nicokant/Work/gisdevio/tasking-manager/frontend
> npm run preparation && npm run update-static && react-scripts build


> TaskingManager-frontend@0.1.0 preparation /home/nicokant/Work/gisdevio/tasking-manager/frontend
> bash -c "if (test -a ../tasking-manager.env); then grep -hs ^ ../tasking-manager.env .env.expand > .env; else cp .env.expand .env; fi"


> TaskingManager-frontend@0.1.0 update-static /home/nicokant/Work/gisdevio/tasking-manager/frontend
> bash -c "mkdir -p public/static/id; mkdir -p public/static/rapid; cp -R node_modules/@hotosm/id/dist/* public/static/id; if ! (test -a node_modules/RapiD/dist/RapiD.css) then mv node_modules/RapiD/dist/iD.css node_modules/RapiD/dist/RapiD.css; fi; cp -R node_modules/RapiD/dist/* public/static/rapid;"

Creating an optimized production build...
Failed to compile.

./src/components/horizontalScroll/styles.scss
globalThis is not defined

Expected behavior
Build successfully

Desktop (please complete the following information):

• OS: Linux Fedora
• TM Version 4.5.2
• Node 10.24.1

[Aadesh-Baral]

@nicokant Can you try it on node 16?

[nicokant]

@Aadesh-Baral I used Node 10 because the frontend dockerfile uses it:
https://github.com/hotosm/tasking-manager/blob/4.5.2/scripts/docker/Dockerfile.frontend#L1

It seems that with Node 16 it works fine but with Node 10 it can't build the image. Is there a CI setup for the project? I think it could help catching these problems :)

[nicokant]

@Aadesh-Baral are docker scripts still maintained?

[Aadesh-Baral]

@nicokant They are not maintained currently. However, it's on our plan to use and maintain docker scripts, and this will probably start soon.

[nicokant]

@Aadesh-Baral I created a PR with node js v16 support, let me know if there's something else I could do to fix this issue.

[ramyaragupathy]

With #5721 - node version moved to 18