I recently discovered this package because I needed to automate the packaging of my extension through a pipeline. However, this is how long it takes to package a small, unrelated extension:
$ time crx pack -o ../my-chrome-extension.crx -p ../my-chrome-extension.pem -b 10000000000 .
crx pack -o ../my-chrome-extension.crx -p ../my-chrome-extension.pem -b 349,10s user 160,66s system 125% cpu 6:44,85 total
The most surprising thing is that my laptop is a good machine! Here are my specs:
--- CPU INFO ---
Architecture: x86_64
CPU(s): 16
On-line CPU(s) list: 0-15
Model name: 11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz
CPU(s) scaling MHz: 76%
NUMA node0 CPU(s): 0-15
--- MEMORY INFO ---
total used free shared buff/cache available
Mem: 31Gi 12Gi 12Gi 1,6Gi 8,8Gi 19Gi
Swap: 5,7Gi 0B 5,7Gi
I wanted to ask if there's something I'm doing wrong or if there's anything I could do to optimize the build time. When I use Chrome's graphical packaging, it takes no time at all.
I recently discovered this package because I needed to automate the packaging of my extension through a pipeline. However, this is how long it takes to package a small, unrelated extension:
The most surprising thing is that my laptop is a good machine! Here are my specs:
--- CPU INFO --- Architecture: x86_64 CPU(s): 16 On-line CPU(s) list: 0-15 Model name: 11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz CPU(s) scaling MHz: 76% NUMA node0 CPU(s): 0-15 --- MEMORY INFO --- total used free shared buff/cache available Mem: 31Gi 12Gi 12Gi 1,6Gi 8,8Gi 19Gi Swap: 5,7Gi 0B 5,7GiI wanted to ask if there's something I'm doing wrong or if there's anything I could do to optimize the build time. When I use Chrome's graphical packaging, it takes no time at all.