Closed Nr9 closed 4 months ago
Overrides were taken out explicitly to solve someone else's issue with them. See #55. I don't have experience with them myself, but if they are essential some time and breaking things some other time, we could make it a configuration option to include/exclude them.
I didn't remember correctly what we did for #55. The overrides from the root manifest are copied over to the isolated manifest. But apparently that is not sufficient for all situations.
Are your overrides specified in the root manifest? What version of PNPM are you using?
I can reproduce the issue with an override in the root manifest with pnpm v9. Possibly the previous solution only worked for v8 or the lockfile pruning that I added later messed things up...
I'm not doing anything special for NPM so possibly it works there because the overrides are being ignored completely.
It appears that the later added prune step is stripping the overrides from the lockfile. I have added them back and published isolate-package@1.17.0-0
under tag next
.
I've tested it on my mono-ts boilerplate and there it works.
Please give it a try an see if it works for you. Then I will publish it as a regular version.
Tested deploy with new version. It works! Thank you.
Using pnpm, when deploying to firebase we have the following error:
The created
pnpm-lock.yaml
does not contain theoverrides
section from the originalpnpm-lock.yaml
Note: we are migrating our project from
npm
topnpm
. Isolate works correctly when usingnpm