Security News
Input Validation Vulnerabilities Dominate MITRE's 2024 CWE Top 25 List
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
Returns the git diff of two strings
git-diff will use git
(if installed) and printf
(if available) to get the real git diff of two strings, viz the actual diff output produced by git itself.
As a fallback, if either command is unavailable, git-diff will instead use the diff module to produce a very good fake git diff.
If desired, you may then console.log the returned git diff. An example of actual output:
npm install --save git-diff
git-diff takes 3 arguments, the old string to diff, the new string to diff and optionally an options object
git-diff returns the git difference or undefined
where there is no difference.
String diff example usage:
var gitDiff = require('git-diff')
var oldStr = 'fred\nis\nfunny\n'
var newStr = 'paul\nis\nfunny\n'
var diff = gitDiff(oldStr, newStr)
var assert = require('assert')
assert.equal(diff, '@@ -1,3 +1,3 @@\n-fred\n+paul\n is\n funny\n')
File diff example usage:
var gitDiff = require('git-diff')
var readFileGo = require('readfile-go') // or your preferred file reader
var oldStr = readFileGo(__dirname + '/oldStr.txt')
var newStr = readFileGo(__dirname + '/newStr.txt')
var diff = gitDiff(oldStr, newStr)
Available options are:
color | flags | forceFake | noHeaders | save | wordDiff
Default options are:
var options = {
color: false, // Add color to the git diff returned?
flags: null, // A space separated string of git diff flags from https://git-scm.com/docs/git-diff#_options
forceFake: false, // Do not try and get a real git diff, just get me a fake? Faster but may not be 100% accurate
noHeaders: false, // Remove the ugly @@ -1,3 +1,3 @@ header?
save: false, // Remember the options for next time?
wordDiff: false // Get a word diff instead of a line diff?
}
Further assistance is given below for options that are not self explanatory.
The flags option allows you to use any git diff flags
This only applies to real git diffs and will not effect the output if it is fake.
An example to illustrate:
var gitDiff = require('git-diff')
var oldStr = 'fred\n is \nfunny\n'
var newStr = 'paul\nis\n funny \n'
var diff = gitDiff(oldStr, newStr, {flags: '--diff-algorithm=minimal --ignore-all-space'})
var assert = require('assert')
assert.equal(diff, '@@ -1,3 +1,3 @@\n-fred\n+paul\n is\n funny \n')
Here, the use of --ignore-all-space
prevents a difference being reported on the 2nd and 3rd lines.
git-diff will initially attempt to use git
and printf
to get the real git diff.
If it cannot, it instead returns a very good fake git diff.
A fake git diff is faster to produce but may not be 100% representative of a real git diff.
The flags option is ignored when faking and fake diffs never have a header.
However, if a fake is good enough and speed is of the essence then you may want to force a fake git diff.
The forceFake option allows you to do exactly that:
var gitDiff = require('git-diff')
var oldStr = 'fred\nis\nfunny\n'
var newStr = 'paul\nis\nfunny\n'
var diff = gitDiff(oldStr, newStr, {forceFake: true})
var assert = require('assert')
assert.equal(diff, '-fred\n+paul\n is\n funny\n')
Its annoying to keep passing the same options every time.
git-diff, if instructed to do so, will remember previously used options for you.
When the {save: true}
option is used in a call to git-diff subsequent calls remember the options.
var gitDiff = require('git-diff')
var oldStr = 'fred\nis\nfunny\n'
var newStr = 'paul\nis\nfunny\n'
var diff1 = gitDiff(oldStr, newStr, {save: true, wordDiff: true})
var diff2 = gitDiff(oldStr, newStr)
var assert = require('assert')
assert.equal(diff1, '@@ -1,3 +1,3 @@\n[-fred-]{+paul+}\nis\nfunny\n')
assert.equal(diff2, '@@ -1,3 +1,3 @@\n[-fred-]{+paul+}\nis\nfunny\n')
Here, the second call remembers that the wordDiff option is on. {wordDiff: true}
is now the default.
git-diff offers a promise based async solution:
var gitDiff = require('git-diff/async')
var oldStr = 'fred\nis\nfunny\n'
var newStr = 'paul\nis\nfunny\n'
gitDiff(oldStr, newStr).then(function(diff) {
var assert = require('assert')
assert.equal(diff, '@@ -1,3 +1,3 @@\n-fred\n+paul\n is\n funny\n')
})
How good is the fake git diff?
The diff module used for the fake diff does not use the same difference algorithm as git. As such, a line diff is likely to be identical to a git line diff whereas a word diff will have some variance.
How can I tell whether the returned git diff is real or fake?
If the@@ -1,3 +1,3 @@
header is present then the returned git diff is real.
If the header is absent then either the noHeaders option is on or the returned git diff is fake.
Will my environment produce a real or fake git diff?
Linux and mac have the covetedprintf
command available. On Windows git bash makesprintf
accessible.
Assuming that git is installed, any of these environments will produce a real git diff.
What's the difference between how God treats the righteous and the wicked?
And God saw that the light was good. And God separated the light from the darkness. Genesis 1:4 ESV
And He will do it again:
Let both grow together until the harvest, and at harvest time I will tell the reapers, “Gather the weeds first and bind them in bundles to be burned, but gather the wheat into my barn.” Matthew 13:30 ESV
Much love :D
FAQs
Returns the git diff of two strings
We found that git-diff demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.
Research
Security News
A threat actor's playbook for exploiting the npm ecosystem was exposed on the dark web, detailing how to build a blockchain-powered botnet.