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
The thread started like this: about build speeds of @npm/cli vs pnpm because of its use of TS. What I saw were two things:
pnpm throws out build caches - presumably for "cleanliness" in builds
concurrency is set to 1 - also presumably for safety (?)
The practice to throw out cache & only setting concurrency to 1 completely negates the benefit of TS project references in my opinion. I'm starting a discussion per last tweet on that thread. Intuitively, we know TS takes time to build, yes, but it can be optimized.
So, I think the way to fix this is:
add a separate clean step you can rely on that clears out any built caches & outputs
builds are incremental per TS proj references
add concurrency to something appropriate for the build environment
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
-
Following a discussion that @zkochan started here:
https://twitter.com/ZoltanKochan/status/1459137137517936688?s=20
The thread started like this: about build speeds of
@npm/cli
vspnpm
because of its use of TS. What I saw were two things:pnpm
throws out build caches - presumably for "cleanliness" in buildsThe practice to throw out cache & only setting concurrency to 1 completely negates the benefit of TS project references in my opinion. I'm starting a discussion per last tweet on that thread. Intuitively, we know TS takes time to build, yes, but it can be optimized.
So, I think the way to fix this is:
clean
step you can rely on that clears out any built caches & outputsBeta Was this translation helpful? Give feedback.
All reactions