search

thom4parisot / grunt-crx

Grunt task used to package private Chrome Extensions.
https://npmjs.com/grunt-crx
MIT License
118 stars 21 forks source link

Enable introspection of the /tmp directory contents #30

Closed jasonkarns closed 8 years ago

jasonkarns commented 11 years ago

I would like to see more detailed output of which exact files were packed into the crx file. Running with verbose flag shows the files that were deleted from /tmp, but that doesn't help determine if all the necessary exclude files were listed correctly. (We have a non-trivial list of excludes.)

This behaviour could be implemented by listing out the actual contents of /tmp (after the excludes are deleted). Or, running in debug mode could just leave the /tmp directory intact after the task runs.

thom4parisot commented 11 years ago

That's a good idea, the dry run.

If it's just a matter of checking what's included/excluded by the src config attribute though, it's doable but not very specific nor relevant to this task.

If the extension leverages the use of src, the verbose flag will indeed display the list of files used by the task, which I think will also help addressing the problem.