building gzweb 1.4.0 against node 12 (Gazebo11/ROS2)

[newcanopies]

Can gzweb be deployed against node 12?
rclnodejs (of ros2-web-bridge) module implementation requires Node 12.

Ubuntu Focal 20.04
ROS2 Foxy, Gazebo 11

STEPS:
git checkout gzweb_1.4.0 (as per install instructions)
source /usr/share/gazebo/setup.sh
APPLIED Binding gyp & deploy.sh PATCHES
enable write permissions for deploy script
sudo chmod +x ./scripts/deploy.sh

npm run deploy --- -m local

> gzweb@1.3.0 deploy /home/user/gzweb
> ./deploy.sh "-m" "local"

Build a local model database.
Only local models.
npm WARN ajv-keywords@2.1.1 requires a peer of ajv@^5.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN gzweb@1.3.0 No license field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

audited 769 packages in 5.439s

10 packages are looking for funding
  run `npm fund` for details

found 54 vulnerabilities (23 low, 11 moderate, 20 high)
  run `npm audit fix` to fix them, or `npm audit` for details
Running "concat:build_src" (concat) task

Running "concat:build_gz3d" (concat) task

Running "concat:build_gui" (concat) task

Running "jshint:files" (jshint) task
>> 2 files lint free.

Running "uglify:build_src" (uglify) task
>> 1 file created 1.48 MB → 693.93 kB

Running "uglify:build_gz3d" (uglify) task
>> 1 file created 1.48 MB → 693.93 kB

Running "uglify:build_gui" (uglify) task
>> 1 file created 2.13 MB → 1.14 MB

Done, without errors.
-- The C compiler identification is GNU 9.3.0
-- The CXX compiler identification is GNU 9.3.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- gzweb version 2.0.0
CMake Warning (dev) at CMakeLists.txt:23 (set):
  Policy CMP0053 is not set: Simplify variable reference and escape sequence
  evaluation.  Run "cmake --help-policy CMP0053" for policy details.  Use the
  cmake_policy command to set the policy and suppress this warning.

  For input:

    '@PROJECT_NAME@-@GZWEB_VERSION_FULL@'

  the old evaluation rules produce:

    'gzweb-2.0.0'

  but the new evaluation rules produce:

    '@PROJECT_NAME@-@GZWEB_VERSION_FULL@'

  Using the old result for compatibility since the policy is not set.
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Build type not selected: Release selected by default
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.1") 
CMake Error at CMakeLists.txt:38 (find_package):
  By not providing "Findgazebo.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "gazebo", but
  CMake did not find one.

  Could not find a package configuration file provided by "gazebo" with any
  of the following names:

    gazeboConfig.cmake
    gazebo-config.cmake

  Add the installation prefix of "gazebo" to CMAKE_PREFIX_PATH or set
  "gazebo_DIR" to a directory containing one of the above files.  If "gazebo"
  provides a separate development package or SDK, be sure it has been
  installed.


-- Configuring incomplete, errors occurred!
See also "/home/user/gzweb/build/CMakeFiles/CMakeOutput.log".
There are cmake errors, exiting.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! gzweb@1.3.0 deploy: `./deploy.sh "-m" "local"`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the gzweb@1.3.0 deploy script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/user/.npm/_logs/2021-01-22T13_44_42_730Z-debug.log

$ npm start

> gzweb@1.3.0 start /home/user/gzweb
> if [ $npm_config_port ]; then port=$npm_config_port; fi; cd gzbridge && ./server.js $port

internal/modules/cjs/loader.js:818
  throw err;
  ^

Error: Cannot find module './build/Debug/gzbridge'
Require stack:
- /home/user/gzweb/gzbridge/server.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:815:15)
    at Function.Module._load (internal/modules/cjs/loader.js:667:27)
    at Module.require (internal/modules/cjs/loader.js:887:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at Object.<anonymous> (/home/user/gzweb/gzbridge/server.js:9:18)
    at Module._compile (internal/modules/cjs/loader.js:999:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
    at Module.load (internal/modules/cjs/loader.js:863:32)
    at Function.Module._load (internal/modules/cjs/loader.js:708:14)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:60:12) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ '/home/user/gzweb/gzbridge/server.js' ]
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! gzweb@1.3.0 start: `if [ $npm_config_port ]; then port=$npm_config_port; fi; cd gzbridge && ./server.js $port`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the gzweb@1.3.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/user/.npm/_logs/2021-01-22T13_44_57_940Z-debug.log