Fix issue where '--export-on-exit' fails if target dir does not exist #8731
+2
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixes #4688
Currently, running
firebase emulators:start --import does/not/exists --export-on-exitthrows a warning messageError: ENOENT: no such file or directory, mkdir '/Users/alejandromarco/Desktop/firebase-tools/issues/4688/does/not/exists'then the export exitsScenarios Tested
Verified that the directory gets created even if it does not exists
Sample Commands