Conversation
|
|
Deploying repomix with
|
| Latest commit: |
49f93a3
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://814ac02b.repomix.pages.dev |
| Branch Preview URL: | https://feat-website-i18n.repomix.pages.dev |
yamadashy
force-pushed
the
feat/website-i18n
branch
from
96f9126 to
da96eef
Compare
yamadashy
force-pushed
the
feat/website-i18n
branch
from
da96eef to
49f93a3
Compare
|
Warning Rate limit exceeded@yamadashy has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 14 minutes and 45 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📒 Files selected for processing (6)
📝 WalkthroughWalkthroughThis pull request introduces a comprehensive localization and documentation overhaul for the Repomix project. The changes involve creating configuration files and documentation for multiple languages (English, Spanish, Japanese, Korean, Portuguese, and Chinese), with a focus on modular configuration and consistent content across different locales. The project now supports six languages, with detailed guides covering installation, usage, command-line options, security, and development practices. Changes
Possibly related PRs
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Caution
Inline review comments failed to post. This is likely due to GitHub's limits when posting large numbers of comments.
Actionable comments posted: 19
🧹 Nitpick comments (64)
website/client/.vitepress/config/configZhCn.ts (1)
25-25: Consider removing the comment removal sectionThe "注释移除" (Comment Removal) section might not be necessary in the documentation as it's typically an implementation detail rather than a user-facing feature. Consider removing this section to maintain a cleaner documentation structure.
website/client/.vitepress/config/configEs.ts (1)
8-9: Remove unnecessary commentThe comment
// guíais redundant as the text property already indicates this is a guide section.- // guía { text: 'Guía', link: '/es/guide/' },website/client/.vitepress/config/configPtBr.ts (1)
8-9: Remove unnecessary commentThe comment
// guiais redundant as the text property already indicates this is a guide section.- // guia { text: 'Guia', link: '/pt-br/guide/' },website/client/.vitepress/config/configShard.ts (1)
3-3: Consider environment-specific Google Analytics configurationThe Google Analytics tag is hardcoded. Consider making it configurable based on the environment to prevent tracking in development/staging environments.
- const googleAnalyticsTag = 'G-7PTT4PLC69'; + const googleAnalyticsTag = process.env.VITE_GA_TAG || 'G-7PTT4PLC69';Also applies to: 115-130
website/client/src/zh-cn/guide/installation.md (1)
31-38: Verify Docker volume mount security and add warning note.The Docker commands mount the current directory into the container. Consider adding a security note about the implications of mounting directories.
Add a warning note before the Docker commands:
## Docker 安装 使用 Docker 是最便捷的方式之一，可以避免环境配置问题。以下是具体步骤： +::: warning 注意 +在使用 Docker 挂载目录时，请确保您信任要处理的代码，因为这会授予容器对该目录的访问权限。 +::: + ```bashwebsite/client/.vitepress/theme/custom.css (1)
25-32: Add cross-browser support for gradient text.The gradient text effect currently only uses webkit-specific properties. Consider adding fallbacks for other browsers.
Add cross-browser support:
.cli-section h2 { font-size: 2rem; font-weight: 600; margin-bottom: 1.5rem; background: linear-gradient(120deg, #f97316 30%, #ffb25c); -webkit-background-clip: text; -webkit-text-fill-color: transparent; + background-clip: text; + color: transparent; }website/client/src/pt-br/guide/development/index.md (1)
29-29: Add context for the file size limit.The 250-line limit for files needs explanation about its benefits and exceptions.
Add context:
-Mantenha os arquivos com menos de 250 linhas +Mantenha os arquivos com menos de 250 linhas para melhorar a legibilidade e manutenção. Exceções podem ser feitas para casos específicos, como arquivos de configuração complexos.website/client/src/es/guide/development/index.md (1)
27-30: Improve list formatting for better readability.The bullet points need consistent formatting and proper punctuation.
Apply these formatting improvements:
-Usa [Biome](https://biomejs.dev/) para linting y formateo -Inyección de dependencias para la testabilidad -Mantén los archivos por debajo de las 250 líneas -Agrega pruebas para las nuevas funciones +- Usa [Biome](https://biomejs.dev/) para linting y formateo. +- Implementa inyección de dependencias para la testabilidad. +- Mantén los archivos por debajo de las 250 líneas. +- Agrega pruebas para las nuevas funciones.🧰 Tools
🪛 LanguageTool
[typographical] ~27-~27: Mayúsculas y minúsculas recomendadas.
Context: ...e](https://biomejs.dev/) para linting y formateo - Inyección de dependencias para la tes...(AI_ES_GGEC_REPLACEMENT_CASING_LOWERCASE)
[uncategorized] ~27-~27: Probablemente hay un error. Considere aplicar la sugerencia.
Context: ...://biomejs.dev/) para linting y formateo - Inyección de dependencias para la testab...(AI_ES_GGEC_REPLACEMENT_OTHER)
[uncategorized] ~28-~28: Probablemente hay un error. Considere aplicar la sugerencia.
Context: ...ión de dependencias para la testabilidad - Mantén los archivos por debajo de las 25...(AI_ES_GGEC_REPLACEMENT_OTHER)
[uncategorized] ~29-~29: Probablemente hay un error. Considere aplicar la sugerencia.
Context: ...os archivos por debajo de las 250 líneas - Agrega pruebas para las nuevas funciones...(AI_ES_GGEC_REPLACEMENT_OTHER)
website/client/src/ko/guide/comment-removal.md (1)
33-40: Enhance example with more realistic use case.The current example is too simplistic. Consider using a more practical example that better demonstrates the feature's value.
Replace with a more meaningful example:
-// 이것은 한 줄 주석입니다 -function test() { - /* 이것은 - 여러 줄 주석입니다 */ - return true; -} +// 사용자 입력 검증 +function validateUserInput(input) { + /* 입력값이 다음 조건을 만족해야 함: + * - 최소 8자 이상 + * - 특수문자 포함 + * - 공백 없음 + */ + return input.length >= 8 && /[!@#$%^&*]/.test(input) && !/\s/.test(input); +}website/client/src/ja/guide/comment-removal.md (2)
3-3: Consider more concise Japanese expression.より簡潔な表現に修正することを提案します。
-Repomixは、パッケージング時に、ソースコード中のコメントを自動的に削除する機能を提供します。これにより、出力ファイルからノイズを減らし、実際のコードに焦点を当てることができます。 +Repomixは、パッケージング時に、ソースコード中のコメントを自動的に削除します。これにより、出力ファイルからノイズを減らし、実際のコードに焦点を当てます。🧰 Tools
🪛 LanguageTool
[uncategorized] ~3-~3: 「ことができる」という表現は冗長な可能性があります。
Context: ...供します。これにより、出力ファイルからノイズを減らし、実際のコードに焦点を当てることができます。 ## 使用方法 コメントの削除を有効にするには、`repomix.c...(DOUSI_KOTOGADEKIRU)
52-53: Consider adding more specific limitations.制限事項をより具体的に説明することで、ユーザーの理解が深まります。例えば、特定の言語での制限事項や、削除されないコメントの具体例を追加することを推奨します。
website/client/src/es/guide/installation.md (1)
32-38: Enhance Docker command examples with more context.The Docker commands could benefit from additional explanation:
- Clarify the purpose of volume mounting
- Explain the difference between
.and./outputpaths- Add a note about permissions
Add explanatory comments before each command:
# Directorio actual +# Monta el directorio actual para procesar y guardar en el mismo lugar docker run -v .:/app -it --rm ghcr.io/yamadashy/repomix # Directorio específico +# Monta un directorio específico para procesar docker run -v .:/app -it --rm ghcr.io/yamadashy/repomix ruta/al/directorio # Repositorio remoto +# Monta solo el directorio de salida al procesar un repositorio remoto docker run -v ./output:/app -it --rm ghcr.io/yamadashy/repomix --remote yamadashy/repomixwebsite/client/src/zh-cn/guide/remote-repository-processing.md (1)
60-68: Consider expanding the FAQ section.The FAQ section could be enhanced with additional common scenarios:
- Private repository access instructions
- Rate limiting considerations
- Handling repository size limits
- Troubleshooting network issues in detail
website/client/src/ja/guide/custom-instructions.md (1)
37-51: Consider adding input/output encoding information.The XML output example should include information about character encoding to ensure proper handling of Japanese text.
```xml +<?xml version="1.0" encoding="UTF-8"?> <instruction>website/client/src/ko/guide/security.md (1)
64-64: Consider obfuscating the email address.The email address is exposed in plain text, which could lead to spam. Consider using a contact form or obfuscating the email address.
[security]-2. 이메일: koukun0120@gmail.com +2. 이메일: [Contact Form](https://repomix.com/contact)🧰 Tools
🪛 Markdownlint (0.37.0)
64-64: null
Bare URL used(MD034, no-bare-urls)
website/client/src/ja/guide/remote-repository-processing.md (1)
50-51: Use absolute paths for Docker volume mounts.Using relative paths (
.or./output) with Docker volume mounts can be unreliable across different environments. Consider recommending absolute paths for better reliability.-docker run -v .:/app -it --rm ghcr.io/yamadashy/repomix \ +docker run -v "$(pwd)":/app -it --rm ghcr.io/yamadashy/repomix \ --remote user/repo -docker run -v ./output:/app -it --rm ghcr.io/yamadashy/repomix \ +docker run -v "$(pwd)/output":/app -it --rm ghcr.io/yamadashy/repomix \ --remote user/repoAlso applies to: 54-55
website/client/src/ja/guide/security.md (1)
64-64: Consider obfuscating the email address.The email address is exposed in plain text, which could lead to spam. Consider using a contact form or obfuscating the email address.
[security]-2. メール: koukun0120@gmail.com +2. メール: [Contact Form](https://repomix.com/contact)🧰 Tools
🪛 Markdownlint (0.37.0)
64-64: null
Bare URL used(MD034, no-bare-urls)
website/client/src/zh-cn/guide/index.md (1)
17-20: Add language specification to the code block.The fenced code block should specify a language for proper syntax highlighting.
-``` +```text 这个文件包含了仓库中所有文件的合并内容。 我想重构代码，请先帮我审查一下。🧰 Tools
🪛 Markdownlint (0.37.0)
17-17: null
Fenced code blocks should have a language specified(MD040, fenced-code-language)
website/client/src/zh-cn/guide/custom-instructions.md (1)
75-78: Enhance security considerations in the documentation.Consider adding more specific security guidelines about what types of information should not be included in custom instructions, such as:
- API keys or tokens
- Internal infrastructure details
- Business logic that should remain private
- Personal or sensitive data
website/client/src/zh-cn/guide/configuration.md (1)
35-37: Expand security configuration documentation.The security section only shows the basic enablement option. Consider adding:
- Explanation of what the security check covers
- Examples of security issues that can be detected
- Configuration options for customizing security checks
website/client/src/ko/guide/configuration.md (2)
15-28: Consider adding descriptions for configuration options.The configuration example includes
fileSummaryanddirectoryStructureoptions without explaining their purpose or impact. Consider adding descriptions for these options to help users make informed decisions.
35-37: Consider expanding the security section documentation.The security section only shows the
enableSecurityCheckoption. Consider adding more details about:
- What security checks are performed
- How to handle security findings
- Best practices for security configuration
website/client/src/ja/guide/tips/best-practices.md (1)
16-23: Consider adding concrete examples for module separation.While the module separation approach is well explained, it would be beneficial to include concrete examples showing:
- Before/after module separation
- Sample directory structure
- Real-world scenarios
website/client/src/es/guide/custom-instructions.md (2)
17-18: Improve Spanish grammar and punctuation.Add a period after "Instruction" for better readability in Spanish.
Apply this diff:
-El contenido de este archivo se incluirá en la salida bajo la sección "Instruction". +El contenido de este archivo se incluirá en la salida bajo la sección "Instruction".
31-32: Improve Spanish expression.Replace "resultará en" with a more natural Spanish construction.
Apply this diff:
-Esto resultará en la siguiente sección en la salida: +Esto generará la siguiente sección en la salida:🧰 Tools
🪛 LanguageTool
[grammar] ~31-~31: Esta construcción no es adecuada para introducir las consecuencias de una acción.
Context: ...ivo en el directoriotests.Esto resultará en la siguiente sección en la salida:...(RESULTAR_EN)
website/client/src/zh-cn/guide/output.md (1)
89-102: Add language specifiers to code blocks.For better syntax highlighting, add language specifiers to the code blocks:
-``` +```text src/ index.ts utils/ helper.ts文件
File: src/index.ts
-
+typescript
// 文件内容🧰 Tools
🪛 Markdownlint (0.37.0)
94-94: null
Fenced code blocks should have a language specified(MD040, fenced-code-language)
102-102: null
Fenced code blocks should have a language specified(MD040, fenced-code-language)
website/client/src/pt-br/guide/security.md (1)
64-64: Protect email address from scraping.Consider obfuscating the email address to prevent automated scraping.
Apply this diff to obfuscate the email:
-2. Envie um e-mail para: koukun0120@gmail.com +2. Envie um e-mail para: `koukun0120 [at] gmail [dot] com`🧰 Tools
🪛 Markdownlint (0.37.0)
64-64: null
Bare URL used(MD034, no-bare-urls)
website/client/src/ko/guide/output.md (1)
89-94: Add language specifiers to code blocks.Code blocks should specify their language for proper syntax highlighting.
Apply this diff to add language specifiers:
-``` +```text src/ index.ts utils/ helper.ts<details> <summary>🧰 Tools</summary> <details> <summary>🪛 Markdownlint (0.37.0)</summary> 94-94: null Fenced code blocks should have a language specified (MD040, fenced-code-language) </details> </details> </blockquote></details> <details> <summary>website/client/src/ja/guide/prompt-examples.md (1)</summary><blockquote> `6-14`: **Add language specifiers to prompt example blocks.** Code blocks containing prompt examples should specify 'text' as their language. Example fix for the first block: ```diff -``` +```text このコードベースのアーキテクチャを分析してください。 1. 全体的な構造とパターンを評価 2. アーキテクチャ上の潜在的な問題点を特定 3. スケーラビリティ向上のための改善案を提案 4. ベストプラクティスに従っている部分を指摘 保守性とモジュール性に特に注目してください。Apply similar changes to all prompt example blocks in the file.
Also applies to: 17-25, 28-36
🧰 Tools
🪛 Markdownlint (0.37.0)
6-6: null
Fenced code blocks should have a language specified(MD040, fenced-code-language)
website/client/src/ja/guide/output.md (1)
103-103: Add language specifiers to code blocks.Add language specifiers to the fenced code blocks for better syntax highlighting:
-``` +```text src/ index.ts utils/ helper.tsAlso applies to: 111-111
🧰 Tools
🪛 Markdownlint (0.37.0)
103-103: null
Fenced code blocks should have a language specified(MD040, fenced-code-language)
website/client/src/pt-br/guide/output.md (2)
46-46: Improve grammar by adding the article "the".Add the missing article:
-XML format is optimized for AI processing: +The XML format is optimized for AI processing:🧰 Tools
🪛 LanguageTool
[uncategorized] ~46-~46: You might be missing the article “the” here.
Context: ...ormatbash repomix --style xmlXML format is optimized for AI processing: ...(AI_EN_LECTOR_MISSING_DETERMINER_THE)
94-94: Add language specifiers to code blocks.Add language specifiers to the fenced code blocks for better syntax highlighting:
-``` +```text src/ index.ts utils/ helper.tsAlso applies to: 102-102
🧰 Tools
🪛 Markdownlint (0.37.0)
94-94: null
Fenced code blocks should have a language specified(MD040, fenced-code-language)
website/client/src/pt-br/guide/index.md (2)
17-20: Add language specifier to the prompt code block.Add a language specifier to the fenced code block:
-``` +```text Este arquivo contém todos os arquivos do repositório combinados em um só. Eu quero refatorar o código, então, por favor, revise-o primeiro.🧰 Tools
🪛 Markdownlint (0.37.0)
17-17: null
Fenced code blocks should have a language specified(MD040, fenced-code-language)
24-24: Consider localizing image paths.The image paths are in English while the content is in Portuguese. Consider localizing the image paths:
- + - +Also applies to: 28-28
website/client/src/es/guide/index.md (3)
17-20: Add language specifier to the prompt code block.Add a language specifier to the fenced code block:
-``` +```text Este archivo contiene todos los archivos del repositorio combinados en uno. Quiero refactorizar el código, así que por favor revísalo primero.🧰 Tools
🪛 Markdownlint (0.37.0)
17-17: null
Fenced code blocks should have a language specified(MD040, fenced-code-language)
24-24: Localize image paths and alt text.The image paths and alt text are in English while the content is in Spanish. Consider localizing both:
- + - +Also applies to: 28-28
3-3: Fix plural form of acronym.In Spanish, the plural of acronyms should not include the 's':
-modelos de lenguaje grandes (LLMs) +modelos de lenguaje grandes (LLM)🧰 Tools
🪛 LanguageTool
[misspelling] ~3-~3: El plural de las siglas no se marca gráficamente.
Context: ...u código a modelos de lenguaje grandes (LLMs) como Claude, ChatGPT y Gemini. ## Ini...(SIGLAS)
website/client/src/es/guide/output.md (1)
94-94: Add language specifiers to code blocks.Add language specifiers to the fenced code blocks for better syntax highlighting:
-``` +```text src/ index.ts utils/ helper.tsAlso applies to: 102-102
🧰 Tools
🪛 Markdownlint (0.37.0)
94-94: null
Fenced code blocks should have a language specified(MD040, fenced-code-language)
website/client/src/ko/guide/prompt-examples.md (1)
6-6: Add language specifiers to code blocks for better syntax highlighting.Add language specifiers to the fenced code blocks to improve readability and enable proper syntax highlighting.
Example fix for the first code block:
-``` +```textAlso applies to: 17-17, 28-28, 41-41, 50-50, 60-60, 72-72, 83-83, 92-92
🧰 Tools
🪛 Markdownlint (0.37.0)
6-6: null
Fenced code blocks should have a language specified(MD040, fenced-code-language)
website/client/src/en/guide/tips/best-practices.md (1)
35-35: Consider more concise wording.The phrase "grows in size" could be simplified to "expands" or "grows" for better readability.
-By following these practices, you can leverage AI's strengths while building a consistent, high-quality codebase. Even as your project grows in size, each component remains well-defined and manageable. +By following these practices, you can leverage AI's strengths while building a consistent, high-quality codebase. Even as your project grows, each component remains well-defined and manageable.🧰 Tools
🪛 LanguageTool
[style] ~35-~35: ‘grows in size’ might be wordy. Consider a shorter alternative.
Context: ...-quality codebase. Even as your project grows in size, each component remains well-defined an...(EN_WORDINESS_PREMIUM_GROWS_IN_SIZE)
website/client/src/ko/index.md (3)
35-38: Add language specification to the code block.The code block should specify a language for better syntax highlighting and accessibility.
-``` +```text
40-46: Consider localizing image paths for Korean documentation.The image paths use English filenames (
repomix-file-usage-1.png,repomix-file-usage-2.png). Consider using localized image filenames for better maintainability.
48-49: Remove extra empty lines.Multiple consecutive empty lines can be reduced to a single empty line.
website/client/src/ja/index.md (2)
35-38: Add language specification to the code block.The code block should specify a language for better syntax highlighting and accessibility.
-``` +```text🧰 Tools
🪛 Markdownlint (0.37.0)
35-35: null
Fenced code blocks should have a language specified(MD040, fenced-code-language)
40-40: Consider revising the Japanese expression.The expression 「ことができる」 could be simplified for more natural Japanese.
-全体の内容を理解した上で、リファクタリングなどを進めることができます。 +全体の内容を理解した上で、リファクタリングなどを進められます。🧰 Tools
🪛 LanguageTool
[uncategorized] ~40-~40: 「ことができる」という表現は冗長な可能性があります。
Context: ...お願いします。 ``` 全体の内容を理解した上で、リファクタリングなどを進めることができます。 
website/client/src/pt-br/index.md (2)
33-36: Add language specification to the code block.The code block should specify a language for better syntax highlighting and accessibility.
-``` +```text🧰 Tools
🪛 Markdownlint (0.37.0)
33-33: null
Fenced code blocks should have a language specified(MD040, fenced-code-language)
30-31: Improve Portuguese expressions.Consider using "após" instead of "depois de" for more formal documentation.
-Depois de gerar um arquivo compactado +Após gerar um arquivo compactado-Depois de gerar o arquivo compactado +Após gerar o arquivo compactadoAlso applies to: 123-124
🧰 Tools
🪛 LanguageTool
[style] ~30-~30: Substitua por “após”.
Context: ...class="cli-section"> ## Início Rápido Depois de gerar um arquivo compactado (`repomix-o...(DEPOIS_DE_APÓS)
website/client/src/es/index.md (2)
33-36: Add language specification to the code block.The code block should specify a language for better syntax highlighting and accessibility.
-``` +```text🧰 Tools
🪛 Markdownlint (0.37.0)
33-33: null
Fenced code blocks should have a language specified(MD040, fenced-code-language)
1-191: Ensure consistent translation across all language versions.The documentation structure and content are well-maintained across different languages. However, consider implementing a translation management system to ensure long-term consistency and easier updates across all language versions.
🧰 Tools
🪛 Markdownlint (0.37.0)
33-33: null
Fenced code blocks should have a language specified(MD040, fenced-code-language)
🪛 LanguageTool
[uncategorized] ~56-~56: Probablemente hay un error. Considere aplicar la sugerencia.
Context: ...tu proyecto sin necesidad de instalación:bash npx repomixO instalarlo ...(AI_ES_GGEC_REPLACEMENT_PUNCTUATION)
[uncategorized] ~132-~132: Probablemente hay un error. Considere aplicar la sugerencia.
Context: ...puedes ejecutar Repomix usando Docker 🐳 Esto es útil si deseas ejecutar Repomix ...(AI_ES_GGEC_REPLACEMENT_OTHER)
[uncategorized] ~146-~146: Probablemente hay un error. Considere aplicar la sugerencia.
Context: ...to y generar la salida en un directoriooutput: ```bash docker run -v ./output...(AI_ES_GGEC_REPLACEMENT_PUNCTUATION)
[uncategorized] ~146-~146: Probablemente hay un error. Considere aplicar la sugerencia.
Context: ...erar la salida en un directoriooutput: ```bash docker run -v ./output:/app -i...(AI_ES_GGEC_REPLACEMENT_PUNCTUATION)
website/client/src/pt-br/guide/remote-repository-processing.md (2)
66-66: Fix double punctuation.Remove the extra punctuation mark.
-Use `--include` para selecionar caminhos específicos.. +Use `--include` para selecionar caminhos específicos🧰 Tools
🪛 LanguageTool
[uncategorized] ~66-~66: Pontuação duplicada
Context: ...nternet ### Repositórios Grandes - Use--includepara selecionar caminhos especí...(DOUBLE_PUNCTUATION_XML)
48-56: Add security considerations for Docker usage.Consider adding security notes about volume mounting and container permissions.
Add the following section after line 56:
### Considerações de Segurança - Use volumes somente para diretórios necessários - Evite montar diretórios sensíveis - Considere usar um usuário não-root no containerwebsite/client/src/es/guide/usage.md (1)
1-8: Add version compatibility information.Consider adding version compatibility information at the beginning of the usage guide.
Add the following section after line 8:
## Compatibilidad - Node.js: v14.0.0 o superior - npm: v6.0.0 o superiorwebsite/client/src/pt-br/guide/command-line-options.md (1)
57-57: Add environment variables section.Consider adding a section about supported environment variables.
Add the following section:
## Variáveis de Ambiente | Variável | Descrição | Padrão | |----------|-----------|---------| | `REPOMIX_CONFIG` | Caminho do arquivo de configuração | `~/.repomixrc` | | `REPOMIX_IGNORE_SECURITY` | Ignorar verificações de segurança | `false` |website/client/src/es/guide/command-line-options.md (2)
16-16: Fix accent marks in Spanish text.Correct the accent marks in the following words:
-version +versiónAlso applies to: 54-54
🧰 Tools
🪛 LanguageTool
[misspelling] ~16-~16: Posible error de ortografía.
Context: ...| Añadir números de línea |false| |--copy| Copiar al portapapeles |false| | ...(APOSTROFO_ACENTO)
1-71: Ensure consistency with Portuguese version.Add the environment variables section to maintain consistency with the Portuguese documentation.
Add the following section:
## Variables de entorno | Variable | Descripción | Predeterminado | |----------|-------------|----------------| | `REPOMIX_CONFIG` | Ruta del archivo de configuración | `~/.repomixrc` | | `REPOMIX_IGNORE_SECURITY` | Ignorar comprobaciones de seguridad | `false` |🧰 Tools
🪛 LanguageTool
[misspelling] ~16-~16: Posible error de ortografía.
Context: ...| Añadir números de línea |false| |--copy| Copiar al portapapeles |false| | ...(APOSTROFO_ACENTO)
[misspelling] ~27-~27: Si es pasado, se escribe con tilde. Si es imperativo, puede que falte una coma.
Context: ...nes a incluir (separados por comas) | |-i, --ignore <patrones>| Patrones a ignorar (separ...(SUBJUNTIVO_PASADO)
[misspelling] ~54-~54: Posible error de ortografía.
Context: ...escripción | |--------|-------------| |-v, --version| Mostrar versión | |--verbose| Hab...(APOSTROFO_ACENTO)
🪛 Markdownlint (0.37.0)
56-56: Expected: 2; Actual: 3; Too many cells, extra data will be missing
Table column count(MD056, table-column-count)
website/client/src/pt-br/guide/tips/best-practices.md (1)
3-3: Consider revising the introductory statement to be more authoritative.The current introduction might undermine the credibility of the advice that follows. Consider rephrasing to focus on the valuable insights gained from experience rather than highlighting the lack of large-scale project completion.
-While I haven't successfully completed a large-scale project using AI yet, I'd like to share what I've learned so far from my experience working with AI in development. +Based on my experience working with AI in development, I'd like to share key insights and best practices that have proven effective in various projects.website/client/src/es/guide/development/setup.md (4)
5-7: Add version requirements for npm and Git.For completeness and to prevent compatibility issues, consider specifying the minimum required versions for npm and Git as well.
- Git - npm + Git ≥ 2.0.0 + npm ≥ 8.0.0
29-31: Enhance Docker development instructions.Consider adding:
- Port mapping if the application exposes any ports
- Environment variable configuration
- Docker Compose setup for easier development
# Ejecutar el contenedor -docker run -v ./:/app -it --rm repomix +docker run -v ./:/app -p 3000:3000 -e NODE_ENV=development -it --rm repomixAlso consider adding a
docker-compose.ymlexample for development.
35-41: Add language specifier to the code block and enhance directory structure details.The code block needs a language specifier. Also, consider adding more details about each directory's purpose and key files.
-``` +```text src/ ├── cli/ # Implementación de la CLI ├── config/ # Manejo de la configuración ├── core/ # Funcionalidad principal └── shared/ # Utilidades compartidas + # - utils.ts: Utilidades comunes + # - types.ts: Tipos compartidos<details> <summary>🧰 Tools</summary> <details> <summary>🪛 Markdownlint (0.37.0)</summary> 35-35: null Fenced code blocks should have a language specified (MD040, fenced-code-language) </details> </details> --- `45-56`: **Add test types and success criteria.** Consider adding: 1. Types of tests available (unit, integration, e2e) 2. Expected code coverage thresholds 3. Description of what each linting tool checks ```diff # Ejecutar pruebas npm run test +# Ejecutar pruebas unitarias +npm run test:unit +# Ejecutar pruebas de integración +npm run test:integration # Cobertura de pruebas npm run test-coverage +# Meta: >80% de cobertura total # Linting -npm run lint-biome -npm run lint-ts -npm run lint-secretlint +npm run lint-biome # Estilo y formato de código +npm run lint-ts # Verificación de tipos TypeScript +npm run lint-secretlint # Detección de secretoswebsite/client/src/zh-cn/guide/development/setup.md (1)
35-41: Add language specification to code blockAdd a language identifier to the code block for better syntax highlighting.
-``` +```text src/ ├── cli/ # CLI 实现 ├── config/ # 配置处理 ├── core/ # 核心功能 └── shared/ # 共享工具🧰 Tools
🪛 Markdownlint (0.37.0)
35-35: null
Fenced code blocks should have a language specified(MD040, fenced-code-language)
website/client/src/ko/guide/development/setup.md (1)
35-41: Add language specification to code blockAdd a language identifier to the code block for better syntax highlighting.
-``` +```text src/ ├── cli/ # CLI 구현 ├── config/ # 구성 처리 ├── core/ # 핵심 기능 └── shared/ # 공유 유틸리티🧰 Tools
🪛 Markdownlint (0.37.0)
35-35: null
Fenced code blocks should have a language specified(MD040, fenced-code-language)
website/client/src/ja/guide/development/setup.md (1)
35-41: Add language specification to code blockAdd a language identifier to the code block for better syntax highlighting.
-``` +```text src/ ├── cli/ # CLI実装 ├── config/ # 設定の処理 ├── core/ # コア機能 └── shared/ # 共有ユーティリティ🧰 Tools
🪛 Markdownlint (0.37.0)
35-35: null
Fenced code blocks should have a language specified(MD040, fenced-code-language)
website/client/src/pt-br/guide/development/setup.md (1)
35-41: Add language specification to code blockAdd a language identifier to the code block for better syntax highlighting.
-``` +```text src/ ├── cli/ # Implementação da CLI ├── config/ # Manipulação de configuração ├── core/ # Funcionalidade principal └── shared/ # Utilitários compartilhados🧰 Tools
🪛 Markdownlint (0.37.0)
35-35: null
Fenced code blocks should have a language specified(MD040, fenced-code-language)
🛑 Comments failed to post (19)
website/client/.vitepress/config.ts (1)
7-7:
⚠️ Potential issueFix the typo in the import and usage of 'configShared'
There is a typo in both the import statement and its usage;
configShardshould beconfigShared. This typo will cause module not found errors.Apply this diff to correct the import statement and usage:
-import { configShard } from './config/configShard'; +import { configShared } from './config/configShared'; export default defineConfig({ + ...configShared, - ...configShard, locales: {Also applies to: 11-11
website/client/.vitepress/config/configPtBr.ts (1)
1-44: 💡 Codebase verification
Documentation files are missing for all languages
The verification revealed that none of the documentation files exist in any language. All markdown files referenced in the navigation configurations are missing, including:
- English (default) documentation under
/guide/- Spanish translations under
/es/guide/- Japanese translations under
/ja/guide/- Korean translations under
/ko/guide/- Portuguese translations under
/pt-br/guide/- Chinese translations under
/zh-cn/guide/The documentation structure is properly defined in the config files, but the actual content files need to be created before the site can function properly.
🔗 Analysis chain
Verify the existence of all referenced language files
Each configuration references multiple documentation files under their respective language paths. Let's verify that all these files exist to ensure a complete translation coverage.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Check if all referenced language files exist # Function to extract paths from config files extract_paths() { rg "link: '.*?'" website/client/.vitepress/config/config*.ts -o | \ sed "s/link: '//" | \ sed "s/'$//" | \ grep -v "^http" | \ sort -u } # Get all referenced paths echo "Referenced paths in configs:" extract_paths # Check if the files exist in the docs directory echo -e "\nChecking for missing files:" extract_paths | while read -r path; do # Skip root paths if [[ "$path" == "/" ]]; then continue fi # Construct the full path (append .md if not present) full_path="website/client${path}" if [[ ! "$full_path" =~ \.md$ ]]; then full_path="${full_path}.md" fi # Check if file exists if [ ! -f "$full_path" ]; then echo "Missing: $full_path" fi doneLength of output: 73194
Script:
#!/bin/bash # Description: Check if all referenced language files exist (corrected path handling) # Function to extract paths from config files extract_paths() { rg "link: '.*?'" website/client/.vitepress/config/config*.ts -o | \ sed "s/link: '//" | \ sed "s/'$//" | \ grep -v "^http" | \ sort -u } # Get all referenced paths echo "Referenced paths in configs:" extract_paths # Check if the files exist in the docs directory echo -e "\nChecking for missing files:" extract_paths | while read -r path; do # Skip empty paths if [[ -z "$path" ]]; then continue fi # Handle index files (paths ending with /) if [[ "$path" =~ /$ ]]; then full_path="website/client${path}index.md" else # Append .md if not present full_path="website/client${path}" if [[ ! "$full_path" =~ \.md$ ]]; then full_path="${full_path}.md" fi fi # Check if file exists if [ ! -f "$full_path" ]; then echo "Missing: $full_path" else echo "Found: $full_path" fi doneLength of output: 78797
Script:
#!/bin/bash # Description: Check if all referenced language files exist (with corrected path handling) # Function to extract paths from config files extract_paths() { rg "link: '(/[^']+)'" website/client/.vitepress/config/config*.ts -o | \ sed "s/link: '//" | \ sed "s/'$//" | \ grep -v "^http" | \ sort -u } # Get all referenced paths echo "Referenced documentation paths:" extract_paths # Check if the files exist in the docs directory echo -e "\nChecking for missing files:" extract_paths | while read -r path; do # Skip empty paths if [[ -z "$path" ]]; then continue fi # Handle index files (paths ending with /) if [[ "$path" =~ /$ ]]; then full_path="website/client${path}index.md" else # Append .md if not present full_path="website/client${path}" if [[ ! "$full_path" =~ \.md$ ]]; then full_path="${full_path}.md" fi fi # Check if file exists if [ ! -f "$full_path" ]; then echo "Missing: $full_path" else echo "Found: $full_path" fi doneLength of output: 71464
website/client/.vitepress/config/configShard.ts (2)
19-21: 🛠️ Refactor suggestion
Use HTTPS for sitemap hostname
The sitemap hostname should use HTTPS instead of HTTP for security and SEO benefits.
sitemap: { - hostname: 'http://repomix.com/', + hostname: 'https://repomix.com/', },📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.sitemap: { hostname: 'https://repomix.com/', },
98-111: 🛠️ Refactor suggestion
Ensure consistent use of HTTPS in meta tags
All URLs in meta tags should consistently use HTTPS.
- ['meta', { property: 'twitter:domain', content: 'https://repomix.com' }], + ['meta', { property: 'twitter:domain', content: 'repomix.com' }],Note: The
twitter:domainmeta tag should only contain the domain name without the protocol.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.['meta', { property: 'og:type', content: 'website' }], ['meta', { property: 'og:title', content: 'Repomix' }], ['meta', { property: 'og:site_name', content: 'Repomix' }], ['meta', { property: 'og:image', content: 'https://repomix.com/images/og-image-large.png' }], ['meta', { property: 'og:url', content: 'https://repomix.com' }], ['meta', { property: 'og:description', content: 'Pack your codebase into AI-friendly formats' }], ['meta', { name: 'twitter:card', content: 'summary_large_image' }], ['meta', { property: 'twitter:domain', content: 'repomix.com' }], ['meta', { property: 'twitter:url', content: 'https://repomix.com' }], ['meta', { name: 'twitter:title', content: 'Repomix' }], ['meta', { name: 'twitter:description', content: 'Pack your codebase into AI-friendly formats' }], ['meta', { name: 'twitter:image', content: 'https://repomix.com/images/og-image-large.png' }], ['meta', { name: 'thumbnail', content: 'https://repomix.com/images/og-image-large.png' }],website/client/src/ko/guide/comment-removal.md (1)
52-53: 🛠️ Refactor suggestion
Add warning about preserving important comments.
Consider adding a warning about the importance of preserving certain types of comments.
Add a warning section:
## 참고 - 주석 제거는 행 번호 추가와 같은 다른 처리 단계 전에 수행됩니다. - JSDoc 주석과 같은 일부 주석은 언어 및 컨텍스트에 따라 보존될 수 있습니다. + +::: warning 주의사항 +중요한 라이선스 정보나 법적 고지가 포함된 주석은 제거하지 않도록 주의하세요. +:::📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.- 주석 제거는 행 번호 추가와 같은 다른 처리 단계 전에 수행됩니다. - JSDoc 주석과 같은 일부 주석은 언어 및 컨텍스트에 따라 보존될 수 있습니다. ::: warning 주의사항 중요한 라이선스 정보나 법적 고지가 포함된 주석은 제거하지 않도록 주의하세요. :::website/client/src/zh-cn/guide/comment-removal.md (1)
56-68: 🛠️ Refactor suggestion
Consider adding the "建议用法" (Suggested Usage) section to other language versions.
The Chinese documentation includes valuable additional sections about selective usage, feature combinations, and performance considerations. These sections would be beneficial to add to the Japanese, Spanish, and other language versions for consistency and completeness.
website/client/src/ja/guide/custom-instructions.md (1)
26-26:
⚠️ Potential issueFix inconsistency in language requirement.
Line 26 states that all text should be in English ("すべてのテキストは英語で記述"), but the example instructions are in Japanese. Consider either:
- Providing an English example to match the stated requirement, or
- Clarifying that the language requirement applies only to code comments
website/client/src/zh-cn/guide/index.md (1)
49-54: 🛠️ Refactor suggestion
Consider providing alternative communication channels for Chinese users.
Discord might not be accessible in China. Consider providing alternative communication channels (e.g., WeChat group) for Chinese users.
website/client/src/ja/guide/index.md (1)
17-21: 🛠️ Refactor suggestion
Add language specification to the code block.
The fenced code block should specify a language for proper syntax highlighting.
Apply this change:
-``` +```text🧰 Tools
🪛 Markdownlint (0.37.0)
17-17: null
Fenced code blocks should have a language specified(MD040, fenced-code-language)
website/client/src/ko/guide/index.md (1)
17-21: 🛠️ Refactor suggestion
Add language specification to the code block.
The fenced code block should specify a language for proper syntax highlighting.
Apply this change:
-``` +```text🧰 Tools
🪛 Markdownlint (0.37.0)
17-17: null
Fenced code blocks should have a language specified(MD040, fenced-code-language)
website/client/src/zh-cn/guide/prompt-examples.md (1)
6-14: 🛠️ Refactor suggestion
Add language specifiers to code blocks.
The code blocks are missing language specifiers. Add appropriate language identifiers to improve syntax highlighting and comply with markdown best practices.
Apply these changes:
-``` +```text 分析此代码库的架构： ...Also applies to: 17-25, 27-36
🧰 Tools
🪛 Markdownlint (0.37.0)
6-6: null
Fenced code blocks should have a language specified(MD040, fenced-code-language)
website/client/src/ko/guide/custom-instructions.md (1)
39-44: 🛠️ Refactor suggestion
Fix inconsistency between example input and output.
The output XML example shows slightly different text compared to the input markdown:
- Input: "코딩 지침" vs Output: "코딩 가이드라인"
- Input uses imperative form vs Output uses declarative form
Ensure consistency between input and output examples.website/client/src/zh-cn/guide/command-line-options.md (2)
52-56: 🛠️ Refactor suggestion
Fix table structure for consistency.
The table structure is inconsistent. The
--top-files-lenoption includes a default value but is in a two-column table. Move it to the three-column table format used for other options with default values.Apply this diff:
| 옵션 | 설명 | |--------|-------------| | `-v, --version` | 버전 표시 | -| `--verbose` | 상세 로그 활성화 | -| `--top-files-len <number>` | 표시할 상위 파일 수 | `5` | +| `--verbose` | 상세 로그 활성화 | + +| 옵션 | 설명 | 기본값 | +|--------|-------------|---------| +| `--top-files-len <number>` | 표시할 상위 파일 수 | `5` |Committable suggestion skipped: line range outside the PR's diff.
🧰 Tools
🪛 Markdownlint (0.37.0)
56-56: Expected: 2; Actual: 3; Too many cells, extra data will be missing
Table column count(MD056, table-column-count)
46-48: 💡 Codebase verification
Documentation error in command line options default value
The default value for
--no-security-checkis incorrectly documented astruein the command line options documentation. This contradicts the actual implementation where:
- Security checks are enabled by default (
enableSecurityCheck: true)- The
--no-security-checkflag is used to disable security checks- Therefore, the default value for
--no-security-checkshould befalseThis needs to be corrected in:
- website/client/src/zh-cn/guide/command-line-options.md
- website/client/src/pt-br/guide/command-line-options.md
- website/client/src/ko/guide/command-line-options.md
- website/client/src/ja/guide/command-line-options.md
- website/client/src/es/guide/command-line-options.md
- website/client/src/en/guide/command-line-options.md
🔗 Analysis chain
Verify the default value for security checks.
The documentation shows that security checks are disabled by default (
--no-security-checkistrue). This seems counterintuitive from a security perspective. Please verify if this is the intended behavior.🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Check the actual default value in the source code ast-grep --pattern 'const defaultConfig = { $$$ security: { enableSecurityCheck: $_ } $$$ }'Length of output: 106
Script:
#!/bin/bash # Search for security check related code and configuration rg -i "security.*check|securitycheck" -A 3 -B 3 # Search specifically for the CLI option rg -i "no-security-check" -A 3 -B 3 # Find all documentation files for command line options fd "command-line-options" --type fLength of output: 64819
website/client/src/ja/guide/command-line-options.md (1)
52-56:
⚠️ Potential issueFix table structure inconsistency.
The table has a mismatch in column count. The header defines two columns but line 56 contains three cells.
Apply this diff to fix the table structure:
| オプション | 説明 | |--------|-------------| -| `--top-files-len <number>` | 上位何件のファイルを詳細出力するかを指定する | `5` | +| `--top-files-len <number>` | 上位何件のファイルを詳細出力するかを指定する（デフォルト: 5） |📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.| オプション | 説明 | |--------|-------------| | `-v, --version` | バージョンを表示 | | `--verbose` | 詳細なログ出力を有効化 | | `--top-files-len <number>` | 上位何件のファイルを詳細出力するかを指定する（デフォルト: 5） |🧰 Tools
🪛 Markdownlint (0.37.0)
56-56: Expected: 2; Actual: 3; Too many cells, extra data will be missing
Table column count(MD056, table-column-count)
website/client/src/pt-br/guide/command-line-options.md (1)
52-56:
⚠️ Potential issueFix table column count inconsistency.
The table has an inconsistent number of columns. Add the missing column header.
| Opção | Descrição | |--------|-------------| -| `-v, --version` | Mostrar versão | -| `--verbose` | Habilitar logging detalhado | -| `--top-files-len <número>` | Número de arquivos principais para mostrar | `5` | +| Opção | Descrição | Padrão | +|--------|-------------|---------| +| `-v, --version` | Mostrar versão | - | +| `--verbose` | Habilitar logging detalhado | `false` | +| `--top-files-len <número>` | Número de arquivos principais para mostrar | `5` |📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.| Opção | Descrição | Padrão | |--------|-------------|---------| | `-v, --version` | Mostrar versão | - | | `--verbose` | Habilitar logging detalhado | `false` | | `--top-files-len <número>` | Número de arquivos principais para mostrar | `5` |🧰 Tools
🪛 Markdownlint (0.37.0)
56-56: Expected: 2; Actual: 3; Too many cells, extra data will be missing
Table column count(MD056, table-column-count)
website/client/src/es/guide/command-line-options.md (1)
52-56:
⚠️ Potential issueFix table column count inconsistency.
The table has an inconsistent number of columns. Add the missing column header.
| Opción | Descripción | |--------|-------------| -| `-v, --version` | Mostrar versión | -| `--verbose` | Habilitar el registro detallado | -| `--top-files-len <número>` | Número de archivos principales a mostrar | `5` | +| Opción | Descripción | Predeterminado | +|--------|-------------|---------| +| `-v, --version` | Mostrar versión | - | +| `--verbose` | Habilitar el registro detallado | `false` | +| `--top-files-len <número>` | Número de archivos principales a mostrar | `5` |📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.| Opción | Descripción | Predeterminado | |--------|-------------|---------| | `-v, --version` | Mostrar versión | - | | `--verbose` | Habilitar el registro detallado | `false` | | `--top-files-len <número>` | Número de archivos principales a mostrar | `5` |🧰 Tools
🪛 LanguageTool
[misspelling] ~54-~54: Posible error de ortografía.
Context: ...escripción | |--------|-------------| |-v, --version| Mostrar versión | |--verbose| Hab...(APOSTROFO_ACENTO)
🪛 Markdownlint (0.37.0)
56-56: Expected: 2; Actual: 3; Too many cells, extra data will be missing
Table column count(MD056, table-column-count)
website/client/src/es/guide/development/setup.md (2)
58-73: 🛠️ Refactor suggestion
Enhance release process documentation.
The release process should include additional important steps:
- Updating the changelog
- Creating git tags
- Creating GitHub releases
## Proceso de lanzamiento -1. Actualizar la versión +1. Actualizar CHANGELOG.md + +2. Actualizar la versión ```bash npm version patch # o minor/major-2. Ejecutar pruebas y construir
+3. Ejecutar pruebas y construirnpm run test-coverage npm run build-3. Publicar
+4. Crear tag y release
+bash +git push origin main --tags +gh release create v$(node -p "require('./package.json').version") +
+
+5. Publicarnpm publish--- 19-21: _:bulb: Codebase verification_ **The CLI command is correct, but configuration setup needs documentation.** The `npm run cli-run` command is valid and properly defined in package.json. However, the setup guide should mention that users need to create a `repomix.config.json` file with basic configuration options like output settings and ignore patterns. <details> <summary>🔗 Analysis chain</summary> **Verify the CLI execution command and add configuration steps.** The `npm run cli-run` command seems non-standard. Additionally, consider adding steps for setting up any required environment variables or configuration files. Let me verify the package.json scripts: </details> <details> <summary>🏁 Scripts executed</summary> The following scripts were executed for the analysis: Script: ```shell #!/bin/bash # Check if cli-run script exists in package.json jq '.scripts["cli-run"]' package.json # Look for alternative CLI-related scripts jq '.scripts | keys[] | select(contains("cli"))' package.jsonLength of output: 170
Script:
#!/bin/bash # Look for configuration files fd -e json -e yaml -e yml -e env config fd -e json -e yaml -e yml -e env -e example .env # Search for environment variable usage in the CLI file rg -A 2 'process.env' bin/repomix.cjs # Search for configuration loading in the CLI file rg -A 2 'config|configuration' bin/repomix.cjsLength of output: 409
Script:
#!/bin/bash # Check main config file echo "Main config:" cat repomix.config.json # Check test fixture config echo -e "\nTest fixture config:" cat tests/integration-tests/fixtures/packager/inputs/simple-project/repomix.config.jsonLength of output: 1589
|
Caution No docstrings were generated. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #293 +/- ##
=======================================
Coverage 92.20% 92.20%
=======================================
Files 44 44
Lines 2168 2168
Branches 474 474
=======================================
Hits 1999 1999
Misses 169 169 ☔ View full report in Codecov by Sentry. |
1 participant
Checklist
npm run testnpm run lint