Creating a containerized TabFern Build environment

People,

I have a few issues to respond to but before I did I thought I would get a reliable TF build situation going which I thought would clarify how I should respond to some of the issues. However, I had trouble following the stuff here:

https://github.com/cxw42/TabFern/blob/master/CONTRIBUTING.md

I am getting an error on my Fedora Linux setup. I try really hard NOT to direct installs of software, preferring, if I possibly can, to install RPM packages - so, thinking that the problem was a Fedora-realted pkg problem, I thought I would get a Docker node.js container (ie Debian based) going so I could do the TF build in there instead of on my Fedora workstation. So I did that (although used Podman instead of Docker) - but I get the same error . . so I don't think it was a Fedora problem after all. Doing:

 # npm install

I get:

Build failed with error code: 1
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! node-sass@4.9.4 postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the node-sass@4.9.4 postinstall 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!     /root/.npm/_logs/2020-05-04T05_33_32_079Z-debug.log

Am I missing something?

Thanks, Phil.

cxw42 / TabFern

Creating a containerized TabFern Build environment #211