tschaub / grunt-newer

Configure Grunt tasks to run with newer files only.
https://npmjs.org/package/grunt-newer
MIT License
944 stars 53 forks source link

Optionally compare files based on md5sum #5

Open tschaub opened 11 years ago

tschaub commented 11 years ago

I'm inclined to create a new task for this: different. The benefit of the first is clearer semantics and the ability to use newer and different within a single gruntfile.

tschaub commented 11 years ago

Work in progress on the md5sum branch.

iigorr commented 10 years ago

:+1: We need this.

Sparticuz commented 10 years ago

:+1: I like to clean out my build directory so I know I'm starting from a clean slate

Driklyn commented 9 years ago

:+1:

Any progress on this? Would like to start using this plugin, but it doesn't seem very practical if it only works with "newer" files... When switching between branch A and branch B in git, you're bound to have files that are different (i.e. older) and need to be recompiled in order to get said branch to run properly. Otherwise, you may still be running code from branch A when working in branch B (unless when switching between branches, you ran through your tasks once without using newer -- which would be bothersome and hard to remember).

inversion commented 9 years ago

I've picked up work from the md5sum branch on my fork - we'd also find it useful for the git branch switching scenario, will make a pull request linked to this issue when I'm done.

EDIT: However I just found https://github.com/researchgate/grunt-changed which may do all of this. In that case perhaps it is better to keep two separate plugins?

tschaub commented 9 years ago

Looks strikingly similar :).

@inversion I'd be curious to hear if grunt-changed meets your needs. It would be nice if the two tasks could share a common core. I'd be in support of working with @researchgate or anyone else on that effort.

danez commented 9 years ago

researchgate/grunt-changed is basically also a fork of grunt-newer, but changed to work on filechanges. If you have ideas on how we could share stuff between this two projects, we are also open put effort into this.

I also think having two plugins is probably better. If it would be one plugin with a config switch like method: 'content/timestamp/...' then there would need to be support of having different configurations to use in one gruntfile, as people might like to use different compare methods for different tasks and not sure if that would be easy possible. But you already mentioned the same in the first post.