Simplify @corpuscule/element about corpuscule HOT 1 CLOSED

Thinking about moving @computed decorator to a separate package I've thoght that it might be not a good idea. Since decorators are going to be a part of language, different decorator libraries will appear eventually. Furthermore, @computed is a common tool to implement and there is going to be a lot of implementations.

So creating a separate package in Corpuscule scope looks redundant. It would be better to create a separate module in @corpuscule/element that exports @computed decorator. So it will be accessible to anyone who uses CorpusculeElement and won't pollute npm's Corpuscule scope with packages.

from corpuscule.