-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Fixing extensions path recognition #8331
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Thanks for working on this issue! Couple of things:
|
To 1, TIL: https://learn.microsoft.com/en-us/dotnet/standard/io/file-path-formats#canonicalize-separators - I'll edit this to recognize both on windows. To 2, that's almost certainly an unrelated issue coming from inside your code base - maybe ping the extensions team on chat for assistance if needed? |
I thought so too, but it did deploy when accessing the globally installed version of firebase-tools with |
Hmmm, does it occur even if you point at the latest published version throuhg npx (ie If both those fail, my guess is that this is an unrelated issue with loading functions code when running thru npx that is showing up oddly due to poor error handling |
Description
Fixes #8326