See 9101704.

@scottgonzalez Thanks. Maybe having grunt npmcopy as a postinstall script wouldn't be bad. I've heard postinstall scripts are discouraged although I don't know why.

That would potentially put you in a dirty state immediately though, right? That doesn't sound great.

If you touch package.json, it's good that it gets you in a dirty state so that you don't forget to commit everything. If files match, this will be a noop.

Assuming the person making the change is manually changing package.json and then using npm install. If the changes are made with npm install --save-dev some-package, then the postinstall script won't run.

A postinstall would help us remember, but we don't want users and one-time contributors to have to deal with it.

If the changes are made with npm install --save-dev some-package, then the postinstall script won't run.

Right. :/ Not a good idea then.