You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use Projen for project scaffolding and config generation across my monorepos (tsconfig, pyproject.toml, eslint, jest, package.json, GitHub workflows, etc.). Projen has its own task system (.projen/tasks.json) and deps (.projen/deps.json), and I'm curious how Moon users handle the overlap.
What I'd love to hear
Is anyone using Moon + Projen together? How did you draw the line between them?
Do you let Moon own all task orchestration and use Projen purely for config generation? Or do you keep projen's task system for some things (release, bump, etc.)?
Any gotchas or friction points with the two coexisting?
For polyglot monorepos (e.g. TypeScript + Python), how has the experience been?
Any shared experiences, tips, or warnings welcome. Thanks!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hey everyone 👋
I use Projen for project scaffolding and config generation across my monorepos (tsconfig, pyproject.toml, eslint, jest, package.json, GitHub workflows, etc.). Projen has its own task system (
.projen/tasks.json) and deps (.projen/deps.json), and I'm curious how Moon users handle the overlap.What I'd love to hear
Any shared experiences, tips, or warnings welcome. Thanks!
Beta Was this translation helpful? Give feedback.
All reactions