aalej

Results 105 comments of aalej

Hey @exetico, sorry to hear you're still encountering this issue, and thanks for all the additional details. I appreciate your effort in gathering this information! I’m also now able to...

Hey @sangaritta, thanks for the feedback. Currently, since the Firebase CLI does not support passing build arguments, to workaround this you could try changing `"source": "."` to `"public": "build/web"` in...

Thanks for reviewing @dlarocque! sorry I missed adding the changeset - added the changeset in commit https://github.com/firebase/firebase-js-sdk/pull/9399/commits/f863b7b09a5a66bd40089fb1825ee31fa38b9c38

Hey @JonathonPenberthy, sorry to hear you encountered this issue and thanks for reporting this. Based on the error message, it looks like the cause of this might be related to...

Hey @7hokerz, thanks for reporting this. At the moment, I can’t seem to reproduce the issue. If you are encountering an error running the deploy command on the Firebase CLI,...

Hey @7hokerz , sorry I wasn't able to get back to this sooner. Taking a look into this again, I can’t seem to reproduce the issue locally. I used the...

> That's weird. I just tested it just in case, and I get the same error. Since you're encountering the same error using the same codebase and dependencies, I'm guessing...

That's good news! Though, I think this might also be an issue we'd encounter when folks upgrade to npm v11. Will share this update with our engineering team.

Just a quick update here, I did a couple more testing and it seems like the issue might be with npm, specifically v11.6.1 and v11.6.2. The reason I think this...

Hey @unav4ila8le, I tried with npm v11.6.3 and v11.6.4 and both seem to work fine. Used the [mcve](https://github.com/aalej/tools-issue-9295_npm) I shared in the npm issue https://github.com/npm/cli/issues/8725 and no errors are being...