Reduce the "scripts/optimize-images.ts" script runtime, potentially by keeping track of what images have already been reduced so the script does not have to resize all of the images on every build.
This script is run on each build of the site, thus reducing the runtime is beneficial for reducing the build times.
Reduce the "scripts/optimize-images.ts" script runtime, potentially by keeping track of what images have already been reduced so the script does not have to resize all of the images on every build.
This script is run on each build of the site, thus reducing the runtime is beneficial for reducing the build times.
I don't think this would reduce the run-time of the script, but it might be worth considering optimizing/resizing the event images as well. (I believe we are currently only optimizing the Meet the Team images.) For example, the recent Bondfire and CxC images are like 4000x4000, and most of the others are still 1000x1000 which is much larger than we need.
The main reason why I bring this up is because recently when I ran the script locally, I noticed it got stuck processing the Bondfire and CxC images...
I don't think this would reduce the run-time of the script, but it might be worth considering optimizing/resizing the event images as well. (I believe we are currently only optimizing the Meet the Team images.) For example, the recent Bondfire and CxC images are like 4000x4000, and most of the others are still 1000x1000 which is much larger than we need.
The main reason why I bring this up is because recently when I ran the script locally, I noticed it got stuck processing the Bondfire and CxC images...
snedadah
added reference shahanneda/optimze-image-script8 months ago
snedadah
Reduce the "scripts/optimize-images.ts" script runtime, potentially by keeping track of what images have already been reduced so the script does not have to resize all of the images on every build.
This script is run on each build of the site, thus reducing the runtime is beneficial for reducing the build times.
oops, closed it by accident 🙈
I don't think this would reduce the run-time of the script, but it might be worth considering optimizing/resizing the event images as well. (I believe we are currently only optimizing the Meet the Team images.) For example, the recent Bondfire and CxC images are like 4000x4000, and most of the others are still 1000x1000 which is much larger than we need.
The main reason why I bring this up is because recently when I ran the script locally, I noticed it got stuck processing the Bondfire and CxC images...