-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DX w/ monorepo tooling #803
Comments
There are just two subprojects (backend and frontend), so it felt like an overkill to introduce extra tooling for that. My plan was to use P.S. |
As of my experience, in this kind of setup (just client and server) package.json is usually shared. |
Meh, I don't think it is a good idea to mix client and server dependencies / commands since that may cause various unexpected issues. P.S. I am all for improvements to documentation 👍 |
This might do it. |
Story
As a developer who just started working on projects, I stumbled upon a bump while bootstrapping the app. The repository seems to be monorepo, but lacks appropriate tooling (e.g.
lerna
,pnpm
). There is no instruction for a developer to runnpm i
in every folder you're going to work in, and defaultnpm i
in root folder didn't help much. Combining with wild-card module declaration (which is in my belief smelly code by itself) it caused me to dig for some time why every module in project is broken and linked to wildcard module declaration.Proposals
The text was updated successfully, but these errors were encountered: