I'm getting deploy errors on previously deployable functions. I think because I was messing around with firebase app initialization in two different files. I'm using Github Codespaces.
A few options:
try to learn how to revert current codespace to a previous commit
debug the existing deploy errors to get my current environment back on track
start a new codespace from a previous commit and re-initialize my environment in the new codespace
manually delete the breaking changes I think I introduced
So far, trying to debug in my existing codespace has caused new deploy errors to replace the old ones, so I'm thinking of cutting my losses somehow.
If I could easily click a button and reboot my codespace to an older version, I would do that, but I'm not very familiar with source control in Codespaces, especially reverting.
Right now the plan for the upcoming pomodoros will be to try remove offending code and redo package.json and package-lock.json.
Error details:
Build failed: npm ERR! Cannot read property '@firebase/app' of undefined
Previous errors included trouble unpacking a package hosted in a personal private repo (which was fixed by a package-lock.json rebuild), and then separate dependency error, which I can give more details about soon.
3/19/2023
up to 3.5 pomodoros. Current environment doesn't feel salvagable. Feel like it might be easier to try to rescue this from an older commit and rebuild the Firebase project in a new environment. Still skeptical that things will go smoothly from there as it feels like this might be part of what I'm dealing with: Upgrade to Node.js SDK Admin SDK v10 (modular SDK) | Firebase Admin SDK (google.com)
3/20/2023
4.5 pomodoros done.
I went back a few commits and reinstalled firebase-tools and, um, I was successfully able to redeploy a function. I need to try it on a few more before declaring victory.
4.7 pomodoros done: oooff just ran into the original error message that kicked off all this nonsense.
5.5 the original error is a checksum sha-512 integrity issue with a self-made module. Most of these solutions seem to not work or break things further: javascript - npm install: Verfication failed while extracting - Stack Overflow
5.8 pomodoros
Was able to deploy one of the previously undeployable functions. Deploying a second function and will test to see that new logs show up and that it doesn't have errors. If it does not, I think this will be a success.
6 pomodoros
All done.
1,000🏅 Top traders
| # | Name | Total profit |
|---|---|---|
| 1 | Ṁ26 |
@AashiqDheeraj77eb The project ends when I can redeploy a function, regardless of where I do it from. So migrating off codespaces would still be part of the project. All approaches toward being able to redeploy a function fall under that umbrella and the pomodoro count continues.
If I give up entirely on the notion of being able to redeploy a function before I’ve spent the MAX 20 pomodoros on this, I’d be inclined to wait several months to ensure I will not circle back to the project and eventually resolve N/A unless any existing bettors object to that.
This project is vital to being able to modify my product so I would bet very high on a derivative market that this market will not resolve N/A if there’s interest.