[Duplicated] #37

[hexoul]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: /~https://github.com/HAECHI-LABS/vvisp/blob/master/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)
• PR to dev branch

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

Issue Number: #28

$ vvisp -v
error: unknown option `-v'
$ vvisp -version
error: unknown option `-v'
$ vvisp --version
0.1.9

What is the new behavior?

$ vvisp -v
v0.1.9
$ vvisp -version
v0.1.9
$ vvisp --version
v0.1.9

Does this PR introduce a breaking change?

• Yes
• No

Other information

Even if it was described as feature in #28, there are no tests because it is just version display.

[JhChoy]

Thank you for the first contribute!
There is just one request.
Could you change the fix: update README for vvisp npm badge commit msg to docs: update README for vvisp npm badge please?
Then, I'll go on to merge :)

[hexoul]

OMG I missed branch control. because of recreated branch, can't reopen it. Please see #37