Skip to content
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

[Monorepo] Enforce task order #65

Open
beefchimi opened this issue Jan 15, 2024 · 0 comments
Open

[Monorepo] Enforce task order #65

beefchimi opened this issue Jan 15, 2024 · 0 comments
Labels
🛠️ Tooling Relating to build tooling or deployment

Comments

@beefchimi
Copy link
Owner

At the moment, I am just using pnpm for all of our monorepo needs. Ideally, I keep it this way... as I don't really want to introduce additional tools and over complicate things.

But, the main issue we have is that pnpm doesn't really allow any explicit "task order". Example:

  • I want to run some tasks in parralel.
  • Application B consumes Package A.
    • The build of Package A needs to be present for Application B to consume.
  • There is no garuntee that the build step for Package A will be run before the build step of Application B.

A tool like nx can be used to orchestrate the order in which dependencies are built. I did experiment with this, but ultimately felt it wasn't worth the added tooling.

Alternative solution

Honestly - at least for the codebase in its form today - all we really need is to point directly to the earwurm source (rather than its /dist) when in local development.

If only there was some additional config for a package.json that allowed you to declare a "local dev import path".

Possible leads:

@beefchimi beefchimi added the 🛠️ Tooling Relating to build tooling or deployment label Jan 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🛠️ Tooling Relating to build tooling or deployment
Projects
None yet
Development

No branches or pull requests

1 participant