changesets - npm Package Compare versions

Comparing version 0.2.0 to 0.2.1

component.json

lib/text/Changeset.js

		@@ -204,2 +204,3 @@ /*!
		Changeset.unpack = function(packed) {
		if(packed == '') return new Changeset
		var matches = packed.match(/(\+\|-)\w+?:[^:]+?:\w+?/g)
		@@ -206,0 +207,0 @@ if(!matches) throw new Error('Cannot unpack invalid serialized changeset string')

package.json

		@@ -1,4 +0,4 @@
		{
		{
		"name": "changesets",
		"version": "0.2.0",
		"version": "0.2.1",
		"description": "A Changeset library incorporating an operational transformation (OT) algorithm -- for node and the browser!",
		@@ -5,0 +5,0 @@ "repository": {

README.md

		@@ -19,6 +19,6 @@
		## Install
		`npm install changesets`
		`npm install changesets` or `component install marcelklehr/changesets`

		## Usage
		In node, simply require `'changesets'`
		In node (and using component), simply require `'changesets'`
		```js
		@@ -28,7 +28,7 @@ var cs = require('changesets')

		In the browser, you need to load the package as a browserified javascript file...
		If you're not using component in the browser, you need to load the package as a browserified javascript file...
		```
		<script type="text/javascript" src="node_modules/changesets/client-side.js"></script>
		```
		... in order to be able to use the global `changesets` variable
		... and use the global `changesets` variable ;)

		@@ -137,5 +137,5 @@ ### Constructing and applying changesets
		* Simplify anyundo (large numbers of changesets have to be transformed against each other and an undo changseset)
		* Browsers can run out of memory when en-/decoding large texts in base64, ie. on paste -- it's not ideal
		* Use best effort (aka Fuzzy Patch -- see http://neil.fraser.name/writing/patch/) when applying a changeset, but allow people to check whether the changeset fits neatly, so they can still refuse changesets that don't fit neatly

		# License
		MIT

client-side.js

Sorry, the diff of this file is too big to display

New alerts