ancient-oak - npm Package Compare versions

Comparing version 0.0.5 to 0.0.6

package.json

 {
   "name": "ancient-oak",
-  "version": "0.0.5",
+  "version": "0.0.6",
   "scripts": {
-    "dist": "bin/dist",
-    "docs": "bin/docs",
-    "release": "bin/release",
+    "dist": "scripts/dist",
+    "docs": "scripts/docs",
+    "release": "scripts/release",
     "test": "jasmine-node spec"
@@ -9,0 +9,0 @@ },

README.md

@@ -28,3 +28,3 @@ # Ancient Oak: The Immutable Tree
 For storage Ancient Oak uses exactly the same techniques as Clojure's
-immutable data structures. […]
+immutable data structures. (see [Resources](#resources))
 
@@ -37,14 +37,16 @@ The main difference between Ancient Oak and other JS immutable data
 
-The easiest way to use Ancient Oak in your project is to grab the
-standalone version from [the project
-page](http://szywon.pl/ancient-oak). The library is included on that
-page so you can try it out in your browser's devtools.
+There are three ways of using ancient-oak:
 
-If you're using [browserify](http://browserify.org/), you can use npm
-to bring it in your project:
+- `npm install ancient-oak` for node and browserify projects
+- `bower install ancient-oak` for bower users
+- grab the lib file from http://szywon.pl/ancient-oak
 
-    npm install ancient-oak
+## Resources
 
-## During development
+- talk: [Immutable Data Trees in JavaScript](http://vimeo.com/86694423) by [szywon](http://szywon.pl), (introduction, quite technical, February 2014 at [Ember London](http://emberlondon.com))
+- talk: [Using Persistent Data Structures with Ember.js](http://vimeo.com/89089876) by [Jamie White](http://jgwhite.co.uk) (March 2014 at [Ember London](http://emberlondon.com))
+- article: [Understanding Clojure’s Persistent Vectors](http://hypirion.com/musings/understanding-persistent-vector-pt-1) by Jean Niklas L’orange is a very good write-up on how those data structures work internally
 
+## Included scripts
+
 To generate standalone versions of the library and the docs you can
@@ -56,4 +58,4 @@ run those two commands.
 
-Scripts in `bin/` folder are meant to be run with `npm run` because
-they depend on the environment `npm` is setting for them.
+Scripts in `scripts/` folder are meant to be run with `npm run` because
+they depend on the environment npm is setting for them.
 
@@ -60,0 +62,0 @@ ## Use cases

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

20809

increased by2.63%

Number of lines in readme file

208

increased by0.97%

No dependency changes