Closed joscha closed 9 years ago
@oncletom how about we pass the exclude list into the load
method of the crx
module and pass them on to wrench
- that way we don't have to delete files afterwards, we are just not copying them in the first place. Would you merge a combined PR effort on those two projects?
Hey :-)
Yes of course it would make sense. Although have a look at #36: the globbing has been improved by matching grunt src/dest configuration. I think it would solve this issue.
It just needs to be tested against a real world project before being merged.
What do you think?
ah, nice - yes, that is much better - also goes hand in hand that I actually also need a zip file (for the Chrome webstore) with the same contents as the CRX. What is still missing for #36? Only a test?
Glad to know it works better :-) Thanks for the rebase!
Aso related to your zip need, follow up the thoughts on #19 and it should not be that hard: it's about using src.loadContents
and providing to forward the resulting buffer twice, to crx.pack()
and fs.writeFile
.
A tiny chunk of work is required to be able to untight loadContents
from pack
, as captured by oncletom/crx#23.
And oncletom/crx#23 will do the unsigned archive job.
Thanks @oncletom. I just tried integrating crx#2.0.0
into grunt-crx
- there are some errors in the tests I am not sure how to handle, yet. I will create a PR that references this issue once I got it working.
When trying to package the chrome extension with a
node_modules
folder on the same level as the manifest, the task fails withprobably due to copying the
node_modules
folder as I can see from the createdtmp-XXXXXXX
directory. Even though I have defined thenode_modules
folder to be an exclusion glob: