Provide package information in package.json

[ingomueller-net]

Things like author, license, name, description, etc. Probably remove this information from other places (contributors.txt). Also see issue #7.

---

• Bitbucket: https://bitbucket.org/ingomueller-net/oms-core/issue/9
• Originally reported by: Ingo Müller
• Originally created at: 2015-07-26T14:24:47.961

[ingomueller-net]

See http://browsenpm.org/package.json for documentation.

---

Original comment by: Ingo Müller

[ingomueller-net]

Being this the core, I have the feeling that the "good 'ole contributors.txt" is sufficient, and that we should put the contributors in the json when it's about modules and dependencies

In other words, this seems a little too much "following the textbook" and we don't need to be this strict in writing things where they could (should?) be (just considering that it's not functionality-related!)

That said, I'll keep reading around and perhaps I'll change my mind :D but just notice, that package.json you linked is for npm "applications"/modules (I say that because seems to me when I check scripts) - oms-core isn't a npm module

---

Original comment by: grasshopper

[ingomueller-net]

Ok. I guess we will not deploy it with npm, but with git, so we will not need it.

---

Original comment by: Ingo Müller