Adding commas to the last element of an object or array in package.json can impact how blame is preserved. For example, if we start with this code in commit A:
{
"version": "0.0.1"
}
Then in commit B, another field is added:
{
"version": "0.0.1",
"main": "index.js"
}
When running git blame package.json, both lines are attributed to commit B. To preserve the correct blame, one could add a comma after the first field definition in commit A like this:
{
"version": "0.0.1",
}
However, this syntax is not valid JSON and would raise errors during npm install:
npm ERR! install Couldn't read dependencies
npm ERR! Failed to parse json
npm ERR! Unexpected token } ...
Is there a workaround for this npm error? Can git blame be used creatively to assign blame accurately?