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
At the moment, I am just usingpnpm 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".
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:Application B
consumesPackage A
.Package A
needs to be present forApplication B
to consume.build
step forPackage A
will be run before the build step ofApplication 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:
The text was updated successfully, but these errors were encountered: