Generating .crx doesn't works about crx

[thom4parisot]

@joscha mentioned he regenerated a new pem key. If you do that, does it work?

PS: your key.pem should not be located in the same folder as your manifest, it should be in the parent folder.

[okuryu]

It resolved by regenerate a pem key, Thanks!

[thom4parisot]

@okuryu thanks for the feedback. I wonder what difference between openssl and node-rsa causes that issue though.

[okuryu]

@oncletom @joscha BTW, it seems to changed the extension's ID by regenerating a private pem key. Is there a way to maintains the extension's ID and pem key with using crx module?

[lepolt]

I'm actually having an issue using the crx CLI... I get exceptions from other modules it would seem... Here is my structure:
chrome
/ css
/ html
/ image
/ js
/ libs
manifest.json

$ crx pack
path.js:313
throw new TypeError('Arguments to path.resolve must be strings');
^
TypeError: Arguments to path.resolve must be strings
at exports.resolve (path.js:313:15)
at Command.pack (/usr/local/lib/node_modules/crx/bin/crx.js:60:15)
at Command.listener (/usr/local/lib/node_modules/crx/node_modules/commander/index.js:286:8)
at Command.emit (events.js:98:17)
at Command.parseArgs (/usr/local/lib/node_modules/crx/node_modules/commander/index.js:528:12)
at Command.parse (/usr/local/lib/node_modules/crx/node_modules/commander/index.js:414:21)
at Object. (/usr/local/lib/node_modules/crx/bin/crx.js:35:9)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)

Any quick thoughts? I'd like the app to build my key for me as well.

[cakesmith]

It may be that the pem key was originally generated using the Chrome browser and used the pkcs8 header format and when you regenerated the pem key using the crx CLI, you generated it with the pkcs1 format. Please see pull request #32 which fixes this problem.

[lepolt]

I haven't actually generated a key yet, so key.pem doesn't exist anywhere.

[thom4parisot]

try crx pack .. The CLI misses a default for the path.

[lepolt]

Tried that, it crashes trying to read key.pem since it doesn't exist yet.

[lepolt]

Alright, I see what's going on here... There are a couple assumptions that the CLI is making which is causing the crashes. I'm going to fork, fix, and submit a pull request.

Thanks for your help!

[thom4parisot]

Thank you @lepoltj and sorry for this annoying situation!