feat(--no-runner): added command to do the copy magic without running command at the end #47
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.
Issue
Description
Introduced argument called
--no-runner
which will stop from executingfirebase
or specified insidefireConfig.runner
other command. This functionality introduces a way to use the magic offirebase
without running actual command at the end.Type of change
Notes
With argument
no-runner
no actual script will be executed after the copy logic.This will help us to benefit from the
firelink
to do his magic without running a commandfirebase
or other specified insidefireConfig.runner
. This way we can use the logic for firelink only to prepare the environment and changepackage.json
with appropriate installation directory configured insidefireDependencies
.It is recommended to be used with
--leave-changes
since it will create a temporary file calledpackage-temp.json
in order at some point to revert the side effects from running the command:Revert the changes made inside
package.json