[WIP] Replaced deprecated neutrino config with updated webpack config

[Carla-Moz]

The best way to reduce the number of critical dependency errors was to remove the deprecated neutrino config and replace it with a normal webpack config. Other changes included changing the jest and eslint config since they also used neutrino. Will continue to work on both in this PR to get the dashboards closer to something more modern and stable. For now, the app runs locally at the port 5000 and the netlify deploy is fixed.

Updates:

• Relaxed the eslint rules
• updated the config.yaml and netlify.toml to update node engine to 18.18.0; added .nvmrc with node version as well
• squash commits figuring out config.yaml setup to update node engine in circle ci
• fix the jest config
• fix eslintrc
• fix node version w netlify
• simplify the webpack config

[netlify]

❌ Deploy Preview for firefox-performance-dashboard failed. Why did it fail? →

Name	Link
🔨 Latest commit	8411a7d
🔍 Latest deploy log	https://app.netlify.com/sites/firefox-performance-dashboard/deploys/6789b7f8113259000879f9a0

[davehunt]

Great to see progress here. It looks like the deploy is failing with:

error [email protected]: The engine "node" is incompatible with this module. Expected version "^12.22.0 || ^14.17.0 || >=16.0.0". Got "10.24.1"

Is the idea to keep this PR open until tests/deploy are passing? If so, perhaps we should convert it to a draft until it's ready to land? I'll also remove myself from the reviewers as I don't feel qualified to review these changes.

[Carla-Moz]

Great to see progress here. It looks like the deploy is failing with:

error [email protected]: The engine "node" is incompatible with this module. Expected version "^12.22.0 || ^14.17.0 || >=16.0.0". Got "10.24.1"

Is the idea to keep this PR open until tests/deploy are passing? If so, perhaps we should convert it to a draft until it's ready to land? I'll also remove myself from the reviewers as I don't feel qualified to review these changes.

@davehunt Yes! It's a WIP so I'll be handling the rest of the errors. Once, it's in a good place, I'll remove the WIP flag. I wanted to put it up now to give visibility to work I'm doing on it.

[julienw]

Thanks for these updates!

I pointed out some suggestions and problems. The biggest problems is that the tests don't run :-) and when run they are failing.

But IMO it's fine to have tests failing for now, while you're working on fixing things.

Before landing, I think this should be done:

• simplify the webpack configuration by having just one file and use process.env.NODE_ENV, and get the configuration right
• get tests running (but failing)
• figure out which of .nvmrc or the node_version in netlify.toml is needed and keep one of them if both work (I don't mind which one, I'll let you decide)

The other suggestions can be done in follow-ups IMO.

[julienw]

is this needed with the `.nvmrc? My understanding is that one or the other is needed but not both, and I'm afraid of seeing them different in the future :-)

[julienw]

note that you're not loading the eslint plugin for testing-libary atm (but that's OK, you can always enable it later)