Fixes gimbal node version

[kbardi]

resolves #91

[vercel]

This pull request is being automatically deployed with ZEIT Now (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://zeit.co/aimementoring/website/exevjpd2n
✅ Preview: https://website-git-bugfix-22-node-version.aimementoring.now.sh

[bronz3beard]

Looks good,
I just want to check, do we need any of these plugins for gimbal also?: Available Plugins

[kbardi]

Looks good,
I just want to check, do we need any of these plugins for gimbal also?: Available Plugins

Hey @bronz3beard, yes, I'm having issues loading some gimbal plugins and I do not understand why is that happening...if you can check that would be great

[bronz3beard]

I upgraded modules trying to fix a Gimbal issue and I had to downgrade filestack-react for now to fix build issue. filestack-js known issue

[bronz3beard]

@kbardi
I have fixed the CI workflow, the script and node issue for AWS.

Gimbal is working locally but the rest is really strange! What I have learnt is this.

It has its own version of sqlite3 this is a native module written in some type of C maybe C++ this means it will install the version we need in the used environment architecture, so if we change node version we have to remove and add again these two plugins; so we have the correct sqlite3 version.

@modus/gimbal-plugin-last-value
@modus/gimbal-plugin-sqlite <- sqlite3 is installed with this plugin
NOTE: Gimbal plugins are now not in dev dependencies as i followed exactly install instructions from modus, I thought this could help not sure anymore.

In the action WF, the file that it says is missing node_sqlite3.node can be found locally in my node_modules at /Users/bronzebeard/Desktop/repos/AIME/website/node_modules/@modus/gimbal-plugin-sqlite/node_modules/sqlite3/lib/binding/node-v72-darwin-x64/node_sqlite3.node.

In the action wf it is looking for the file in /github/workspace/node_modules/sqlite3/lib/binding/node-v64-linux-x64/node_sqlite3.node

I cant figure out why this is happening?
These plugins are used to store tests and make comparisons to the last time the test was run.

I could ask Modus but they have not actioned my last issue, so I don't know how quickly we will get a respond to this one also.

I think the issue could be around changing our node version recently, I think sqlite3 is compatible with 12.x, but maybe not the version Gimbal is using as a dependency for a plugin (nested dependencies) which I am 95% sure is v4.1.0?

Maybe this info can help you find an answer, I hope.
If not we may have to wait for the next version of Gimbal, just run it locally or I will find another performance monitoring module for us to use.
Running locally gives some really great results which is great! @camposcristianeze