Thomas Parisot

Hm I see. There is a method to generate a public key: https://github.com/oncletom/crx/blob/120c3611f07e907159580974f85dfcb1b4b8b0dc/src/crx.js#L142-L154 `crx.generateAppId` can give you the extension ID based on the generated public key. Would that work?

I see, that's something I never looked out (their difference of use of the various formats). As far as I can see, it's just a matter of passing a different...

Hello @js-choi, I was not aware of this feature but yes, it would be a good addition. I would indeed favour a `#getExtensionIdFor(publicKeyBuffer)` to return a promise, because the public...

I'd like to learn but I'm not sure it's bringing a lot of value to this project. Do you think it would simplify some aspects of it?

I’m keen on adding a TS definition file. It would be a nice first step. I’m willing to have a go at it while porting the code to be an...

@8bitDesigner well good question, it was not captured as an issue until now ;-) The inner feature is already done, it is basically the `pack` command without `zip` nor `crx`...

@kennynguyeenx is this a sufficient way to work around your initial request? Let us know.

Any hint or reason why?

Hm, so if I understand well, you would like `crx` operations (in the context of webpack), to access the resources you previously stored with `memory-fs`? Isn't it solved by using...

I'm not sure to understand when you use `memory-fs`, is it in the build script, or in the bundle generated by webpack? To confirm, you use `crx` as part of...