add package.json to supported formats

Author: a.pirogov

README.md

@@ -143,9 +143,9 @@ Here is an overview of all the currently supported files and formats.
 
 | Input Formats  | Status | | Target Formats                | Status |
 | -------------- | ------ |-| ----------------------------- | ------ |
-| (.)somesy.toml | ✓      | | pyproject.toml _(poetry)_     | ✓      |
-| pyproject.toml | ✓(1.)  | | pyproject.toml _(setuptools)_ | ✓(2.)  |
-| package.json   | TBD    | | package.json                  | TBD    |
+| (.)somesy.toml | ✓      | | pyproject.toml _(poetry)_       | ✓      |
+| pyproject.toml | ✓(1.)  | | pyproject.toml _(setuptools)_   | ✓(2.)  |
+| package.json   | ✓      | | package.json                  | ✓      |
 |                |        | | mkdocs.yml                    | TBD    |
 |                |        | | CITATION.cff                  | ✓      |
 |                |        | | codemeta.json                 | ✓(3.)  |

docs/manual.md

@@ -305,4 +305,4 @@ everybody's life easier. Furthermore, nobody needs to care whether, under the
 hood, you use `somesy` (or anything like it) or not - they can use the
 corresponding files they already know to get the information they need.
 So there is no "risk" involved in adopting `somesy`, because it does not try to
-abolish any other formats or standards or becoming such.
+abolish any other formats or standards or becoming such.