Hey folks, i tried this out locally and noticed that I am getting the NPM install error there as well.

Looks like we are looking for @dailydotdev/eslint-config externally though I see it is bundled in as a lerna package.

@KyleTryon I forgot to put it back in one commit, should be re-added now.
The main change of this PR is switching from Node 14 to 16, it seems to create some peer dependency issue, but for some reason I can install everything locally.

@KyleTryon I forgot to put it back in one commit, should be re-added now. The main change of this PR is switching from Node 14 to 16, it seems to create some peer dependency issue, but for some reason I can install everything locally.

I have tested again with the latest code in your branch, and I am not able to install it locally. Have you fully deleted your node_modules folder locally before re-installing?

npm ERR! 404 Not Found - GET https://registry.npmjs.org/@dailydotdev%2feslint-plugin-daily-dev-eslint-rules - Not found
npm ERR! 404 
npm ERR! 404  '@dailydotdev/eslint-plugin-daily-dev-eslint-rules@*' is not in this registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)

I have found several examples of similar issues reported with lerna but none that I have seen yet offer much for solutions.

Do we know, is this package meant to be in the registry? Is lerna supposed to be using the local packages rather than attempting to fetch them remotely?

Before releasing it's crucial we do extended tests locally for all three compartments.
webapp - extension and companion.

Also sidenote to update the docs and install steps.

Gitpod perhaps as well

@sshanzel @kirillkurko would love to also get your review on this one