chore(overmind-devtools): ensure deps are explicitly manifested

[dpraimeyuu]

In this tiny PR:

• dependencies were explicitly manifested in package.json - local development can be started
• draft of documentation on the local setup was provided

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[henri-hulski]

I think babel and webpack plug-ins should be under "devDependencies", as they are not used by the runtime but only for development.
You also should make sure that the deps are in sync with the deps in the root of the monorepo. You can check this by running npm run checkdeps from the root folder. After fix it manually as fixdeps doesn't really works as expected.
When you run npm install from the root folder of the monorepo all packages will be linked and build. Don't install dependencies in the package folders as this destroys the linking. All packages should be installed from the root folder during development.
BTW it seems there is a conflict. Make sure you start with the next branch.

[henri-hulski]

BTW I have no idea why npm run start doesn't work for this package.

[dpraimeyuu]

@henri-hulski I'll do how you advised - also documenting in the main readme (?) on how to proceed with bumping and maintaining dependencies.

[henri-hulski]

Sure! I think that would help maintaining overmind.
Another detail, in the monorepo package.json we use exact dependency versions (without the ^) but in the packages we use normal versioning with ^.
Don’t know if this isn't a relic from the time when npm didn't have a lock file and maybe it's not necessary anymore, but for now repo-cooker checks for it.
For more information how repo-cooker works look at its Readme or ask me. 😊