Comparing version 0.1.2 to 0.1.3
{ | ||
"name": "decorative", | ||
"version": "0.1.2", | ||
"version": "0.1.3", | ||
"repository": "https://github.com/kyr0/decorative", | ||
"description": "decorative.js is an ES7 micro-framework promoting @decorator pattern-driven app development.", | ||
@@ -5,0 +6,0 @@ "main": "index.js", |
@@ -14,6 +14,6 @@ decorative.js | ||
It's really "decorative" code you will write using ```@decorators``` ;) | ||
It's really "decorative" code you will be writing using ```@decorators``` ;) | ||
Decorators were introduced to Babel.js in spring 2015 by Yehuda Katz. Since then, only | ||
a few decorators were implemented (see core-decorators). But the world didn't care much, | ||
a few decorators were implemented (see ```core-decorators``` by ```jayphelps```). But the world didn't care much, | ||
no matter if they are amazing or not. | ||
@@ -59,3 +59,3 @@ | ||
Well, now that you got picture. Lets look what we need to run this code | ||
Well, now that you got picture: Lets look what we need to run this code | ||
in today's JS engines. | ||
@@ -65,4 +65,12 @@ | ||
Just install this package like this: | ||
npm install decorative --save | ||
If you also plan to use it with React, you may want to install ```decorative-react```: | ||
npm install decorative-react --save | ||
To use decorative you need to cross-compile the code from tomorrows ECMAScript 7 | ||
code to today's ECMAScript 5 / 6 code. Well, this is quite easy. We use Babel.js | ||
code back to today's ECMAScript 5 / 6 code. Well, this is quite easy. We use Babel.js | ||
and grunt for this. (while gulp is compatible too, I don't have a configuration example yet; feel free to provide one :) | ||
@@ -69,0 +77,0 @@ |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
No repository
Supply chain riskPackage does not have a linked source code repository. Without this field, a package will have no reference to the location of the source code use to generate the package.
Found 1 instance in 1 package
172082
303