Add deeplx-translate extension #24350

ayuayue · 2026-01-10T02:52:36Z

Description

Screencast

Checklist

I read the extension guidelines
I read the documentation about publishing
I ran npm run build and tested this distribution build in Raycast
I checked that files in the assets folder are used by the extension itself
I checked that assets used by the README are placed outside of the metadata folder

raycastbot · 2026-01-10T02:52:53Z

Congratulations on your new Raycast extension! 🚀

Due to our current reduced availability, the initial review may take up to 10-15 business days.

Once the PR is approved and merged, the extension will be available on our Store.

greptile-apps · 2026-01-10T03:29:51Z

Greptile Overview

Greptile Summary

This PR adds a new DeepLX Translate extension for Raycast that provides translation functionality using the DeepLX API. The extension includes a single view-type command with a form interface for translating text between multiple languages.

Key Changes

New extension with translation form UI supporting 12 languages
Configurable API endpoint and optional API key via preferences
Auto-detection for source language and manual target language selection
Translation results displayed in a Detail view with copy actions

Critical Issues Found

Logic Errors:

Target language auto-detection is backwards (line 74-76, 157): The code attempts to detect the language of the input text and use it as the target language, which would result in translating text to the same language (e.g., Chinese→Chinese). Auto-detection should only apply to source language.
Missing metadata folder: Extensions with view-type commands require a metadata/ folder with Raycast-styled screenshots. Currently screenshots are in assets/screenshots/ which doesn't meet store requirements.

Syntax/Compliance Issues:
3. Unnecessary fetch import (line 13): Imports node-fetch despite Node.js 21+ having built-in fetch. The extension uses Node.js 22+ based on dependencies.

Manual Preferences interface (lines 15-18): Manually defines the Preferences interface instead of using auto-generated types from raycast-env.d.ts, which can lead to type mismatches.
Incorrect description (package.json line 5): "use deeplx api translate" should be properly capitalized and grammatically correct.
Future date in CHANGELOG: Lists "2026-01-10" instead of "2025-01-10" for the initial release.

Recommendations

Remove the "auto" option from target language dropdown
Fix the translation logic to only auto-detect source language
Remove node-fetch dependency and import
Use auto-generated Preferences types
Create proper metadata/ folder with Raycast-styled screenshots
Fix description and date formatting issues

Confidence Score: 1/5

This PR has critical logic errors that will cause incorrect translation behavior and violates multiple repository standards
Score reflects two critical functional bugs: (1) backwards target language auto-detection logic that would translate text to the same language, and (2) missing required metadata folder for view-type commands. Additionally, there are multiple violations of repository coding standards including unnecessary dependencies, manual type definitions, and formatting issues. These issues must be resolved before the extension can function correctly and meet store requirements.
Pay close attention to src/translate.tsx (lines 74-76, 157) for the target language logic error and the missing metadata/ folder structure

Important Files Changed

File Analysis

Filename	Score	Overview
extensions/deeplx-translate/src/translate.tsx	1/5	Main translation component with critical logic errors in target language auto-detection and incorrect fetch import
extensions/deeplx-translate/package.json	2/5	Extension manifest with unnecessary node-fetch dependency, incorrect description format, and missing metadata folder
extensions/deeplx-translate/CHANGELOG.md	3/5	Changelog with future date (2026 instead of 2025) for initial release
extensions/deeplx-translate/README.md	4/5	Documentation is clear and comprehensive, though references screenshots in wrong location

greptile-apps

_{8 files reviewed, 8 comments}

_{Edit Code Review Agent Settings | Greptile}

greptile-apps · 2026-01-10T03:29:55Z

extensions/deeplx-translate/src/translate.tsx

+  Icon,
+} from "@raycast/api";
+import { useState } from "react";
+import fetch from "node-fetch";


Do not import fetch from node-fetch in Node.js 21+, as fetch is a built-in global API. Since this extension uses Node.js 22+ (as indicated by the @types/node version 22.13.10), the fetch API is available natively.

Suggested change

import fetch from "node-fetch";

// Remove this import - fetch is built-in in Node.js 21+

greptile-apps · 2026-01-10T03:29:56Z

extensions/deeplx-translate/src/translate.tsx

+interface Preferences {
+  apiEndpoint: string;
+  apiKey?: string;
+}


Don't manually define Preferences interface for getPreferenceValues(). These types are auto-generated in raycast-env.d.ts when the extension runs. Manual definitions can become out of sync with your actual configuration in package.json.

Suggested change

interface Preferences {

apiEndpoint: string;

apiKey?: string;

}

// Remove this manual interface - use auto-generated types from raycast-env.d.ts

greptile-apps · 2026-01-10T03:29:57Z

extensions/deeplx-translate/src/translate.tsx

+      const detectedTargetLang = targetLang === "auto" ? detectLanguage(text) : targetLang;
+      const finalTargetLang = detectedTargetLang || "EN"; // Fallback to English if detection fails
+


This logic is incorrect. The code detects the language of the input text and uses it as the target language. This means if the input is Chinese, it would translate Chinese→Chinese, which doesn't make sense.

Auto-detection should only apply to the source language. The target language should always be explicitly selected by the user. The "auto" option should be removed from the target language dropdown (line 157).

greptile-apps · 2026-01-10T03:29:58Z

extensions/deeplx-translate/src/translate.tsx

+      </Form.Dropdown>
+
+      <Form.Dropdown id="targetLang" title="Target Language" value={targetLang} onChange={setTargetLang}>
+        <Form.Dropdown.Item value="auto" title="Auto Detect" />


The target language dropdown should not have an "auto" option. Auto-detection only makes sense for the source language, not the target. Remove this line.

Suggested change

<Form.Dropdown.Item value="auto" title="Auto Detect" />

<Form.Dropdown id="targetLang" title="Target Language" value={targetLang} onChange={setTargetLang}>

greptile-apps · 2026-01-10T03:29:59Z

extensions/deeplx-translate/package.json

+  "$schema": "https://www.raycast.com/schemas/extension.json",
+  "name": "deeplx-translate",
+  "title": "DeepLX Translate",
+  "description": "use deeplx api translate",


The description should be properly capitalized and grammatically correct. Current: "use deeplx api translate"

Suggested change

"description": "use deeplx api translate",

"description": "Translate text using the DeepLX API",

greptile-apps · 2026-01-10T03:30:00Z

extensions/deeplx-translate/package.json

+  "dependencies": {
+    "@raycast/api": "^1.103.0",
+    "@raycast/utils": "^2.2.1",
+    "node-fetch": "^2.7.0"


This dependency should be removed since fetch is built-in in Node.js 21+. Additionally, if node-fetch were needed, most extensions in this repository use v3 instead of v2.

Suggested change

"node-fetch": "^2.7.0"

// Remove node-fetch dependency - use built-in fetch

greptile-apps · 2026-01-10T03:30:01Z

extensions/deeplx-translate/CHANGELOG.md

+- Add copy translation results to clipboard
+- Improve API settings instructions
+
+## [Initial Release] - 2026-01-10


The date "2026-01-10" is in the future. This should be "2025-01-10" or the actual release date.

Suggested change

## [Initial Release] - 2026-01-10

## [Initial Release] - 2025-01-10

greptile-apps · 2026-01-10T03:30:02Z

extensions/deeplx-translate/package.json

+  "commands": [
+    {
+      "name": "translate",
+      "title": "Translate",
+      "description": "Translate using DeepLX API",
+      "mode": "view",
+      "subtitle": "DeepLX Translation"
+    }
+  ],


Extensions with view-type commands must include a metadata/ folder containing Raycast-styled screenshots. Currently, screenshots are in assets/screenshots/ but they should be in metadata/ instead.

The metadata folder should contain professionally styled screenshots following Raycast's store guidelines. See: https://developers.raycast.com/basics/prepare-an-extension-for-store#screenshots

Add deeplx-translate extension

6a84b6a

raycastbot added new extension Label for PRs with new extensions platform: macOS platform: Windows labels Jan 10, 2026

ayuayue marked this pull request as ready for review January 10, 2026 02:54

raycastbot assigned pernielsentikaer Jan 10, 2026

greptile-apps bot reviewed Jan 10, 2026

View reviewed changes

caoayu added 2 commits January 10, 2026 11:55

Update deeplx-translate extension

154420a

feat(ui): 新增智能备选翻译显示功能

9078d36

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Add deeplx-translate extension #24350

Add deeplx-translate extension #24350

ayuayue commented Jan 10, 2026 •

edited

Loading

Uh oh!

raycastbot commented Jan 10, 2026

Uh oh!

greptile-apps bot commented Jan 10, 2026

Uh oh!

greptile-apps bot left a comment

Uh oh!

greptile-apps bot Jan 10, 2026

Uh oh!

greptile-apps bot Jan 10, 2026

Uh oh!

greptile-apps bot Jan 10, 2026

Uh oh!

greptile-apps bot Jan 10, 2026

Uh oh!

greptile-apps bot Jan 10, 2026

Uh oh!

greptile-apps bot Jan 10, 2026

Uh oh!

greptile-apps bot Jan 10, 2026

Uh oh!

greptile-apps bot Jan 10, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

	import fetch from "node-fetch";
	// Remove this import - fetch is built-in in Node.js 21+

		const detectedTargetLang = targetLang === "auto" ? detectLanguage(text) : targetLang;
		const finalTargetLang = detectedTargetLang \|\| "EN"; // Fallback to English if detection fails

	<Form.Dropdown.Item value="auto" title="Auto Detect" />
	<Form.Dropdown id="targetLang" title="Target Language" value={targetLang} onChange={setTargetLang}>

	"description": "use deeplx api translate",
	"description": "Translate text using the DeepLX API",

	"node-fetch": "^2.7.0"
	// Remove node-fetch dependency - use built-in fetch

	## [Initial Release] - 2026-01-10
	## [Initial Release] - 2025-01-10

Add deeplx-translate extension #24350

Are you sure you want to change the base?

Add deeplx-translate extension #24350

Conversation

ayuayue commented Jan 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Screencast

Checklist

Uh oh!

raycastbot commented Jan 10, 2026

Uh oh!

greptile-apps bot commented Jan 10, 2026

Greptile Overview

Greptile Summary

Key Changes

Critical Issues Found

Recommendations

Confidence Score: 1/5

Important Files Changed

Uh oh!

greptile-apps bot left a comment

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Jan 10, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Jan 10, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Jan 10, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Jan 10, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Jan 10, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Jan 10, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Jan 10, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Jan 10, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

ayuayue commented Jan 10, 2026 •

edited

Loading