The exit code is 0 if there is an exception. I've wrapped the configure and reconfigure to capture exceptions and return with 1 exit code whilst writing to stderr output the exception.
Normalised paths in firebase.json file to ensure they are always forward slashes used in file paths written.
In the integration tests, some line ending normalisation was needed, also need to explicitly run in shell for process.run to work.
Type of Change
[ ] ✨ feat -- New feature (non-breaking change which adds functionality)
[ ] 🛠️ fix -- Bug fix (non-breaking change which fixes an issue)
[ ] ❌ ! -- Breaking change (fix or feature that would cause existing functionality to change)
Description
windows e2e intergration tests.
A few bugs found with windows:
0if there is an exception. I've wrapped theconfigureandreconfigureto capture exceptions and return with1exit code whilst writing tostderroutput the exception.firebase.jsonfile to ensure they are always forward slashes used in file paths written.process.runto work.Type of Change
feat-- New feature (non-breaking change which adds functionality)fix-- Bug fix (non-breaking change which fixes an issue)!-- Breaking change (fix or feature that would cause existing functionality to change)refactor-- Code refactorci-- Build configuration changedocs-- Documentationchore-- Chore