Closed michaelnguyenm closed 6 months ago
"some-project-id" was meant as a placeholder name. You shouldn't deploy to that, unless you actually created a firebase project with that name.
I don't know where this error comes from. I have deployed the services/api this afternoon as a test.
Does it work for you when you roll back to the commit I suggested earlier?
Try deploying with npx firebase deploy --project your-actual-project-id
Apologies as I actually replaced the original project ID in the logs above with some-project-id
. I assure you it's to a real project ID in my Firebase console 😅
It doesn't work when I roll back to the "Fix remeda import"
Strange. I just checked and did a fresh deployment. Deleting the api function first and then redeploying. It works for me.
Did you change anything to the mono-ts codebase maybe? If so, maybe you can try a fresh checkout. I'm out of ideas for now...
Unfortunately I've tried deleting the api function first and doing a fresh checkout, no modifications to the codebase for both the latest revision and for the revision for "Fix remeda import" and even one from about 3 months back, and I still get the ERR_PNPM_OUTDATED_LOCKFILE
after trying to deploy.
I'll try tinkering around some more to see if it's something related to my environment or maybe something related to my firebase project but honestly I'm not sure what could be the issue.
At some point I stopped using the firebase cli (specifically your fork) within Windows Subsystem for Linux (WSL) since I was having trouble logging in and I got it working in WSL again just now. I tried deploying from within WSL instead and it deploys now 🤷
Maybe somehow the lock file generated is slightly different when attempting to deploy from Windows instead of WSL, I have no idea but don't really know if I should try digging into it too much since I know WSL works.
Sorry for the trouble and thanks again for the help and this project.
Not sure if related to #11 but I did try the newest commit. But since this error seems to be different from before and I also tried the commit titled "Fix remeda import", and got the same error, I assume it's related to something else so I opted to create another issue.
I believe I should be using the same lock file that is already included and I'm using the specified version of pnpm set by corepack (8.12.1), so I'm not exactly sure why I'm getting a pnpm related error (though the newest pnpm version is 8.15.5).
I am also using a brand new project (no functions deployed) so I don't have a previously working deployment using this sample repo.
Based on the attached log, I could just find some information about some people having trouble with transitioning between pnpm 7 and 8 https://github.com/pnpm/pnpm/issues/6312 but I don't think that might be the case here since I'm just using all pnpm 8 here. So I'm not exactly sure if there are any other issues to consider.
Specifically this is what I get: