ffmpeggy - npm Package Compare versions

Comparing version 1.0.0 to 1.0.1

package.json

 {
   "name": "ffmpeggy",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "description": "A minimal yet powerful wrapper around ffmpeg and ffprobe",
@@ -64,5 +64,7 @@ "keywords": [
     "semantic-release": "^17.4.4",
+    "tempy": "^1.0.1",
     "tsukuru": "^0.7.2",
     "typed-emitter": "^1.3.1",
-    "typescript": "^4.3.5"
+    "typescript": "^4.3.5",
+    "wait-file": "^1.0.5"
   },
@@ -69,0 +71,0 @@ "release": {

README.md

@@ -53,4 +53,4 @@ # ffmpeggy
     ffmpeg
-      .setInput("file.mp4")
-      .setOutput("file.mkv")
+      .setInput("input.mp4")
+      .setOutput("output.mkv")
       .setOutputOptions(["-c:v h264"])
@@ -76,4 +76,4 @@ .run();
     autorun: true,
-    input: "file.mp4",
-    output: "file.mkv",
+    input: "input.mp4",
+    output: "output.mkv",
     outputOptions: ["-c:v h264"],
@@ -121,3 +121,3 @@ })
   pipe: true, // shorthand for output set to pipe:0
-  input: createReadStream("file.mp4"),
+  input: createReadStream("input.mp4"),
   outputOptions: ["-c:v h264"],
@@ -127,3 +127,3 @@ });
 const stream = ffmpeg.toStream();
-stream.pipe(createWriteStream("file.mkv"));
+stream.pipe(createWriteStream("output.mkv"));
 ```
@@ -138,3 +138,3 @@
 
-const probeResults = await FFmpeg.probe("file.mkv");
+const probeResults = await FFmpeg.probe("input.mkv");
 ```
@@ -204,7 +204,7 @@
 
-Because I wasn't happy with the ones that already exists. Most of them are badly maintained and/or lacking TypeScript typings. I started coding on this a while back for another project and decided it deserved it's own package.
+Because I wasn't happy with the ones that already exists. Most of them are badly maintained, and/or lacking TypeScript typings or are too complex for my taste. I started coding on this a while back for another project and it's been working really well so figured it deserved it's own package.
 
 ## How does ffmpeggy compare from fluent-ffmpeg?
 
-They strive to solve different problems. Whereas ffmpeggy aims to be lean and simple, fluent-ffmpeg aims to provide an exhaustive and human readable API. I personally don't that kind of an API, but I might revisit it at a later stage, but an extended API will most likely end up in a separate package to keep this one as lean as possible.
+They strive to solve different problems. Whereas ffmpeggy aims to be lean and simple, fluent-ffmpeg aims to provide an exhaustive and human readable API. I personally don't need all of that but I might revisit it at a later stage. But an extended API will most likely end up in a separate package to keep this one as lean as possible.
 
@@ -211,0 +211,0 @@ ## License

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

55599

increased by1.1%

Number of package files

46

increased by2.22%

Worsened metrics

Dev dependency count

21

increased by10.53%

No dependency changes