pnpm i -f must be ran after a build, when using depMea.*.injected

[NullVoxPopuli]

due to #49 (comment),
#45 is no longer viable.

See: pnpm/pnpm#6088

[changeset-bot]

⚠️ No Changeset found

Latest commit: 44895c9

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[simonihmig]

Ok, I could have done that as part of #49. But I thought we would be able to land #45...

This is not feasible currently, as the build step triggered by turbo would need to also have pnpm i -f. But still theoretically we could do this? It is just too costly here? More costly than what we have with this PR?

[NullVoxPopuli]

But still theoretically we could do this?

I don't think it's possible -- I opened an issue with turbo here: vercel/turbo#2306 and we tried some solutions, but ultimately, we need to solve: pnpm/pnpm#6088

[simonihmig]

Maybe I am misunderstanding this, but couldn't we just modify the build script to be something like "build": "rollup --config && pnpm i -f",? We are basically doing this here, only at the CI workflow level. Not saying this is nice, but would it work?

[NullVoxPopuli]

on a cache-hit, the entirety of the build script would be skipped, and the links in node_modules/.pnpm not updated

[simonihmig]

Oh, right. This was the missing bit 😔