Update the list and versions of npm packages to fit other governance dapps.
Getting rid of some vulnerable dependencies
Preparation to use npm packages instead of git modules in poa-test-setup to increase speed of preparations for testing of governanance dapps from different branches
Also,
Removing of babel config from package.json. We already have it in .babelrc
Removing of eslintConfig from package.json. We already have it in .eslintrc
Minor prettier fixes
The changes don't break poa-test-setup process flow and do not lead to any changes from UX/UI perspective
(Mandatory) What is it: (Fix), (Feature), or (Refactor) in Title, e.g., "(Fix) price of 1 token in Wei > 18 decimals"
(Refactor)
(Mandatory) Developers: Each completed PR should be updated in the Wiki Documentation.
(Recommended) Each PR should have one commit message and therefore should only contain one specific fix or feature. Otherwise, multiple PRs should be made
Did you check that your PR is chain agnostic? It shouldn't depend on any hardcoded chainIds, URLs.
YES
(Mandatory) Description
poa-test-setupto increase speed of preparations for testing of governanance dapps from different branchesAlso,
babelconfig from package.json. We already have it in.babelrceslintConfigfrom package.json. We already have it in.eslintrcprettierfixesThe changes don't break
poa-test-setupprocess flow and do not lead to any changes from UX/UI perspective(Mandatory) What is it: (Fix), (Feature), or (Refactor) in Title, e.g., "(Fix) price of 1 token in Wei > 18 decimals" (Refactor)
(Mandatory) Developers: Each completed PR should be updated in the Wiki Documentation. (Recommended) Each PR should have one commit message and therefore should only contain one specific fix or feature. Otherwise, multiple PRs should be made
Did you check that your PR is chain agnostic? It shouldn't depend on any hardcoded chainIds, URLs. YES
(Optional) Any additional concerns or comments