Previously the regex used "=>" whereas pep508 specifies ">=" as the ge
comparator. https://www.python.org/dev/peps/pep-0508/#environment-markers

…-pep508

fix: use correct requirements filter regex for 'ge'

this change introduce "--allow-empty" flag, that doesn't throw "No dependencies found." error when manifest is empty.

feat: allow empty manifest flag

today we fail for the following requirements line "-r req-something.txt # some comment" because of the way we split the line
this change will just take the second item in the line (right after the '-r' flag)

in addition, this will fix the release phase on circle

…pace

…n-one-space

fix: when a line inside "requirements.txt" has more than one space

Since the last change of introducing packageToDepTreeMap, we're seeing some errors in logs of "key XXX not found in packageToDepTreeMap"
This happens because current implementation ignores "extras" property (i.e. requests['security']) and identify duplicate "requests" children.
this small change doesn't add support for "extras" property, but simply ignores it in a more graceful way (no regression here)

…eeMap

fix: fix key XXX not found in packageToDepTreeMap

…ip9-support

chore: fix broken tests and remove support for pip 9.0.3

feat: support requirements.txt files with bom enconding

…e-to-16

chore: fix broken tests and bump node to 16

fix: support pipenv empty packages

fix: quote spawn args