Skip to content

Commit 7238cbf

Browse files
Handling of key.pem when path contains spaces
When the path to key.pem contains spaces, the hash does not get generated during development and therefore `key` in manisfest.json goes as a blank string and chrome does not allow loading the unpacked extension. Fixing this issue.
1 parent 06378cb commit 7238cbf

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

lib/signing-key.js

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ exports.generateKey = () => execSync('openssl genrsa 2048 | openssl pkcs8 -topk8
77

88
exports.hashKey = (keyFile) =>
99
new Promise((resolve, reject) => {
10-
exec(`openssl rsa -in ${keyFile} -pubout -outform DER | openssl base64 -A`, (error, stdout) => {
10+
exec(`openssl rsa -in "${keyFile}" -pubout -outform DER | openssl base64 -A`, (error, stdout) => {
1111
if (error) {
1212
// node couldn't execute the command
1313
return reject(error)

0 commit comments

Comments
 (0)