-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
Handle non-monorepo setups #84
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
Add fallback behavior for non-monorepos.
If no monorepo setup is detected we can still move the files to the isolate directory or do something else without throwing an error. This could allow the firebase-tools fork to always execute isolate and we wouldn't have to opt-in, making it a zero-config upgrade.
The text was updated successfully, but these errors were encountered: