Root package.json is possibly useless

Following #94, it looks like I introduced the root package.json file as a “fix” to some GitHub security notification in #20. However, two things strike me as strange:

• Instead of bumping the versions in frontend/package.json, I created a whole new one, which doesn’t really make sense;
• I bumped the lodash version even though lodash is not listed in the project’s frontend dependencies. Moreover, @types/lodash is listed as DevDependencies although lodash isn’t.

I guess I was pretty tired when I made those changes, but they were harmless so I consider myself lucky.

A suggested course of action:

• Bump react-app-rewire-webpack-bundle-analyzer in frontend/package.json to 1.1.0 (to fix the initial security issue) and run the yarn analyze command in frontend to see if it’s still working correctly;
• Remove the @types/lodash dev dependency and run yarn start to see if no TS errors appear.

This would have the following benefits:

• Fix the security issue in react-app-rewire-webpack-bundle-analyzer
• Clean up the repository
• Ease up the setup of the Falco project locally as, for now, people may be tempted to run yarn && yarn start in the root dir instead of frontend/

This PR is up for grabs if anyone’s interested (maybe @toqueteos?)!

[phacks]

@toqueteos Sorry to hear that, thanks for giving it a go! I’ll try on my end to fix this and hope that I’ll be luckier.

[phacks]

Oooh, good catch! Here’s my output of yarn why lodash:

➜  frontend git:(master) yarn why lodash
yarn why v1.17.3
[1/4] 🤔  Why do we have the module "lodash"...?
[2/4] 🚚  Initialising dependency graph...
[3/4] 🔍  Finding dependency...
[4/4] 🚡  Calculating file sizes...
=> Found "lodash@4.17.11"

Hope that helps!