joye61 / pic-smaller Goto Github PK

默认配置下对比效果：
压缩前：

压缩后：

如题，批量操作中很多时候是同一批次的摄影，有些是纵向的有些是横向的。如果能添加如题功能，可以有效提高操作效率。

看下结果。

zhe这是原图。你自己可以试下。

个人感觉要是有本地离线版本就更好，这样可以不受网络及域名失效的影响，隐私更得到保障

比如我原图可能是16:9或者4：3，可以选择1:1裁切， 直接最短边居中就行，或者原图1:1，居中最短边裁切成4:3之类的。

主要是现在这些电商太折腾了，产品图要1：1，但是笔记图又推荐其他尺寸，心累。

刚下午安装运行，样式全是乱的，node v18.18.0

如上图所示。

macOS上，明明多选了N张往里面一起拖，不管怎么操作，实际拉进去的只有一张图。

Background

As our project grows, maintaining a consistent coding style across multiple files and developers becomes increasingly challenging. This can lead to discrepancies in code formatting, which may not only affect readability but also lead to unnecessary git diffs that complicate code reviews and version control.

Proposal

I propose that we integrate Prettier, an opinionated code formatter, into our development workflow. Prettier supports many languages and integrates well with most editors and the command line. By automating the formatting process, we can ensure our codebase remains clean and consistent without requiring manual effort from developers.

Benefits

1. Consistency: Automates formatting to ensure all developers follow the same style without having to think about it.
2. Saves Time and Reduces Errors: Minimizes the time spent on formatting code manually, allowing developers to focus more on logic and implementation.
3. Enhanced Code Quality: Improves readability and reduces the likelihood of format-related issues in code reviews.
4. Easy Integration: Prettier can be easily integrated with pre-commit hooks using tools like Husky, ensuring that all committed code is automatically formatted.

Implementation Steps

1. Agree on the basic Prettier configuration settings that match our project's coding standards.
2. Set up Prettier with a configuration file in our project repository.
3. Integrate Prettier into our build process using a pre-commit hook to automatically format staged files.
4. Update our contributing guidelines to include steps for setting up Prettier locally.

Seeking Feedback

I would like feedback on:

• The choice of Prettier as our code formatter.
• Any specific preferences for Prettier configurations (e.g., tab width, semicolons, single vs double quotes).
• How to best integrate this into our existing workflow without disrupting current project timelines.

Please share your thoughts and suggestions on this proposal. Your input is invaluable as we aim to enhance our development practices.

RT, 方便构建 h5 游戏后使用脚本调用 api 自动压缩等需要自动化压缩的情况

我看到在Thanks里面列出了Gif、PNG、avif使用的压缩库，那JPEG使用的什么库呀😊

下载文件时，建议考虑让用户选择保存路径

因为在压缩图片后，一般就是要覆盖原图片的，选择路径可以找到上传目录，方便直接覆盖

现在默认是浏览器的下载目录，下载后还需手工剪切图片到原目录

可以参考一下squoosh.app
看看提供了多少调整选项，以及还可以进行格式转换

你好，请问怎么编译部署到二级目录呢？

是否可以通过 GitHub Action 的方式自动构建 docker 镜像并且发布到 Docker Hub 或者 ghcr，这样既方便普通用户私有部署，也可以通过 watchtower 等工具自动更新镜像，而不需要用户在仓库更新之后手动拉取代码、本地构建镜像。

感谢大佬辛勤开发，希望项目越来越好！