duckfactory - npm Package Compare versions

Comparing version 1.2.5 to 1.2.6

lib/functionArgNames.js

		@@ -6,2 +6,9 @@ 'use strict';
		});

		var _stringify = require('babel-runtime/core-js/json/stringify');

		var _stringify2 = _interopRequireDefault(_stringify);

		function _interopRequireDefault(obj) { return obj && obj.__esModule ? obj : { default: obj }; }

		/** Returns an array with the names of the direct names of a function (e.g. for the function a = (b, c) => {}
		@@ -25,4 +32,7 @@ * getFunctionArgNames(a) will return ["b", "c"]).
		var getFunctionRefsNames = function getFunctionRefsNames(func, ref) {
		console.log("func:", func.toString);
		console.log("ref:", (0, _stringify2.default)(ref));
		var pattern = new RegExp(ref + "\\.([a-zA-Z0-9_]+)[\\,\\;]", 'g');
		var args = func.toString().match(pattern);
		console.log("args:", (0, _stringify2.default)(args));
		return args && args.map(function (arg) {
		@@ -29,0 +39,0 @@ return arg.slice(ref.length + 1, arg.length - 1);

package.json

		{
		"name": "duckfactory",
		"version": "1.2.5",
		"version": "1.2.6",
		"description": "Factory for creating redux ducks",
		@@ -5,0 +5,0 @@ "main": "lib/index.js",

README.md

		@@ -0,1 +1,9 @@
		## IMPORTANT:
		A naughty bug has been discovered! It causes a problem (loss of action creator arguments) when duckfactory is used in projects that use code mangling (code minification / uglification) for production with tools like webpack.

		I'm currently working on this and will release a bugfix version when it's solved. Until then I don't recommend using duckfactory (v1.2.6 or below) or goosefactory (version 1.2.7 or below) with production-mangled code.


		---

		# Duckfactory
		@@ -2,0 +10,0 @@ Simple creation and use of redux ducks.

New alerts