reactifex - npm Package Compare versions

Comparing version 1.0.0 to 1.0.1

main.js

@@ -28,3 +28,2 @@ #!/usr/bin/env node
   fs.writeFileSync(scriptPath, "#!/bin/bash\n");
-  fs.writeFileSync(scriptPath, "set -x\n");
   inData.forEach((message) => {
@@ -42,5 +41,4 @@ var info = messageInfo.find(mi => mi.key == message.id);
   });
-  fs.writeFileSync(scriptPath, "set +x\n");
 } else {
   fs.writeFileSync(process.argv[3], JSON.stringify(outData, null, 2));
 }

package.json

 {
   "name": "reactifex",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "description": "A helper for moving react-intl messages to transifex and back",
@@ -8,3 +8,4 @@ "bin": "./main.js",
     "lint": "eslint .",
-    "test": "node main.js test_data/input/ test_data/test_output.json && diff test_data/test_output.json test_data/expected_output/messages.json"
+    "test_compile": "node main.js test_data/input/ test_data/test_output.json && diff test_data/test_output.json test_data/expected_output/messages.json",
+    "test_comments": "node main.js test_data/input/ --comments && diff bash_scripts/put_comments.sh test_data/expected_output/put_comments.sh"
   },
@@ -11,0 +12,0 @@ "repository": {

README.md

@@ -26,4 +26,2 @@ # reactifex
 
-Note that tests for this mode aren't included, as it relies on Transifex's API being up and responsive.
-
 Usage is a little complicated, I'm sorry about that; you're going to be running this server-side as a series of bash commands. Do note that I assume `$SECRET_USER` and `$SECRET_PWD` env vars exist for basic auth purposes. See [Transifex's API Introduction](https://docs.transifex.com/api/introduction) for more details on authentication. Here's an example, written as it would be in the Makefile of a project that makes use of reactifex:
@@ -30,0 +28,0 @@

No alert changes

Improved metrics

Total package byte prevSize

10257

18.14%

Number of package files

13

8.33%

Lines of code

107

17.58%

Worsened metrics

Number of lines in readme file

44

-4.35%

No dependency changes