fluxy - npm Package Compare versions

Comparing version 0.4.2 to 0.4.3

examples/todomvc-flux/js/components/TodoApp.react.js

@@ -60,3 +60,3 @@ /**
     var allTodos = TodoStore.toJS(this.state.allTodos);
-  	return (
+    return (
       <div>
@@ -63,0 +63,0 @@ <Header />

examples/todomvc-flux/package.json

@@ -9,8 +9,9 @@ {
     "express": "^4.6.1",
+    "body-parser": "^1.5.2",
     "node-jsx": "^0.11.0",
     "st": "^0.5.1",
-    "fluxy": "jmreidy/fluxy"
+    "fluxy": "jmreidy/fluxy",
+    "bluebird": "^1.2.4"
   },
   "devDependencies": {
-    "browserify": "~2.36.0",
     "envify": "~1.2.0",
@@ -21,6 +22,8 @@ "reactify": "~0.4.0",
     "uglify-js": "~2.4.13",
-    "watchify": "~0.4.1"
+    "watchify": "~0.4.1",
+    "react-tools": "^0.11.0",
+    "browserify": "^8.1.1"
   },
   "scripts": {
-    "build": "STATIC_ROOT=./static NODE_ENV=production browserify -o assets/js/bundle.js -e js/app.js",
+    "build": "STATIC_ROOT=./static NODE_ENV=production ./node_modules/.bin/browserify -o assets/js/bundle.js -e js/app.js",
     "server": "npm run-script build && node server"
@@ -27,0 +30,0 @@ },

examples/todomvc-flux/README.md

@@ -50,3 +50,3 @@ # Fluxy TodoMVC Example
 You must have [npm](https://www.npmjs.org/) installed on your computer.
-From the root project directory run these commands from the command line:
+From the example's root directory run these commands on the command line:
 
@@ -60,3 +60,3 @@ npm install
 First, as a client side only app (via static HTML), just run `npm run-script build` and
-then start a http server that makes the index.html file accessible (via, say, `httpster`).
+then start a http server that makes the index.html file accessible (via, say, [`httpster`](https://github.com/SimbCo/httpster)).
 
@@ -63,0 +63,0 @@ Alternatively, you can run an express server that will enable server side rendering. To do so,

lib/Dispatcher.js

@@ -95,17 +95,16 @@ /**
 
-    if (arguments.length > 2) {
-      payload = Array.prototype.slice.call(arguments, 1);
-    }
-    else {
-      payload = [payload];
-    }
-
     if (!this._currentDispatch || this._currentDispatch.isResolved()) {
-        this._currentDispatch = Promise.map(
-            handlers,
-            function (handler, idx) {
-              return self._activatePromise(idx, handler, payload);
-            }
-        );
-        this._currentDispatch.finally(this._processQueue.bind(this));
+      if (arguments.length > 2) {
+        payload = Array.prototype.slice.call(arguments, 1);
+      }
+      else {
+        payload = [payload];
+      }
+      this._currentDispatch = Promise.map(
+        handlers,
+        function (handler, idx) {
+          return self._activatePromise(idx, handler, payload);
+        }
+      );
+      this._currentDispatch.finally(this._processQueue.bind(this));
     }
@@ -112,0 +111,0 @@ else {

package.json

 {
   "name": "fluxy",
-  "version": "0.4.2",
+  "version": "0.4.3",
   "description": "",
@@ -27,3 +27,3 @@ "main": "index.js",
     "commander": "^2.2.0",
-    "enum": "^0.2.6",
+    "enum": "^2.1.0",
     "lodash-node": "^2.4.1",
@@ -30,0 +30,0 @@ "minimist": "^0.2.0",

README.md

@@ -11,3 +11,3 @@ [![Build Status](https://travis-ci.org/jmreidy/fluxy.svg?branch=master)](https://travis-ci.org/jmreidy/fluxy)
 the React documentation. Distilled to its core, Flux reimagines the
-tradtional MVC approach to client-side webapps, replacing it with the
+traditional MVC approach to client-side webapps, replacing it with the
 same concept of "one-way data flow" that powers React.
@@ -21,3 +21,3 @@
 All application data is managed in Stores, which are Singleton objects focused on a specific
-set of business logic (e.g ArticleStore, UserStore). Views should intereact with Stores
+set of business logic (e.g ArticleStore, UserStore). Views should interact with Stores
 as the single source of data truth. Store *do not replace* the React state system; rather,
@@ -64,3 +64,3 @@ React components should use state to handle view-specific data state, and stores to handle application
 objects: Stores, Actions, and Constants. While these three types of objects operate
-in concert, their roles are very distrint from one another - in fact, a Store should
+in concert, their roles are very distinct from one another - in fact, a Store should
 never call an Action, and an Action should never call into a Store. Instead, the Dispatcher
@@ -175,3 +175,3 @@ unifies Action and Store objects, with messages defined by Constants. (All of the details
 to the [Enum](https://github.com/adrai/enum) constructor. `messages` and `servicesMessages` have
-equivalent key and value pais. `values` have a string key and a variable value.
+equivalent key and value pairs. `values` have a string key and a variable value.
 
@@ -178,0 +178,0 @@ `serviceMessages` perform the same helpful function as `serviceActions` above - they accomodate for

New alerts

Major refactor

Supply chain risk

Package has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.

Found 1 instance in 1 package

Improved metrics

Number of package files

48

increased by2.13%

Worsened metrics

Total package byte prevSize

97750

decreased by-91.55%

Lines of code

2517

decreased by-91.14%

Number of medium supply chain risk alerts

1

increased byInfinity%

Dependency changes

• + Addedenum@2.5.0(transitive)

• + Addedis-buffer@1.1.6(transitive)

• - Removedenum@0.2.7(transitive)

• Updatedenum@^2.1.0