Add morse-code-reader extension

[arefur-rahman]

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]

Congratulations on your new Raycast extension! 🚀

We're currently experiencing a high volume of incoming requests. As a result, 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.

[arefur-rahman]

I needed a morse code reader tool in my hand but I didn't found any extensions for this purpose. and it's not worthy to install a new application in my laptop so I built it.

[greptile-apps]

Greptile Summary

This PR adds a new morse-code-reader extension that converts text to Morse code and vice versa, with auto-detection of the input type and clipboard copy support.

• @raycast/utils is declared as a dependency in package.json but is never imported anywhere in the source — it should be removed.
• The extension's metadata/ folder with Raycast Store screenshots is missing, which is required for view-type commands before publishing.
• The category is set to \"Security\", which doesn't fit a Morse Code translator; \"Fun\" is more appropriate.

Confidence Score: 3/5

Not ready to merge — missing store metadata screenshots and has an unused dependency that needs to be removed

Two P1s (unused dependency, missing metadata folder) and three P2s; the missing metadata/ folder is a blocking store requirement

extensions/morse-code-reader/package.json (unused dependency + wrong category); extensions/morse-code-reader/ root (missing metadata/ folder with screenshots)

Important Files Changed

Filename	Overview
extensions/morse-code-reader/package.json	@raycast/utils listed as a dependency but never imported; category "Security" is incorrect for a Morse Code tool
extensions/morse-code-reader/src/morse-code-reader.tsx	Core Morse Code conversion logic and Raycast Form UI; output textarea silently discards user edits (should use Form.Description)
extensions/morse-code-reader/CHANGELOG.md	Informal title and non-standard [Initial Version] label; {PR_MERGE_DATE} placeholder is correctly present
extensions/morse-code-reader/.prettierrc	Correctly uses printWidth: 120 and singleQuote: false per Raycast standards
extensions/morse-code-reader/eslint.config.js	Correctly uses defineConfig from eslint/config with the Raycast ESLint config

Prompt To Fix All With AI

This is a comment left during a code review.
Path: extensions/morse-code-reader/package.json
Line: 25-26

Comment:
**Unused dependency: `@raycast/utils`**

`@raycast/utils` is declared as a dependency but is never imported in `src/morse-code-reader.tsx` (the only source file). This bloats the bundle unnecessarily.

```suggestion
    "@raycast/api": "^1.104.13"
```

**Rule Used:** What: Every dependency listed in package.json must... ([source](https://app.greptile.com/review/custom-context?memory=bffc60eb-f9f2-4219-b804-76e29e267d43))

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: extensions/morse-code-reader/package.json
Line: 21-23

Comment:
**Missing `metadata/` folder with store screenshots**

The command uses `"mode": "view"`, so Raycast Store guidelines require a `metadata/` folder containing at least one Raycast-styled screenshot. Without it, the extension cannot be published to the store. See the [screenshots docs](https://developers.raycast.com/basics/prepare-an-extension-for-store#screenshots) for the required format.

**Rule Used:** What: Extensions with view-type commands must incl... ([source](https://app.greptile.com/review/custom-context?memory=87059ac1-c601-487f-9f1c-bce8a3cb6209))

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: extensions/morse-code-reader/package.json
Line: 12-14

Comment:
**Incorrect category for a Morse Code extension**

`"Security"` is reserved for extensions like password managers and secrets tools. A Morse Code translator fits `"Fun"` (novelty/entertainment tool) or possibly `"Developer Tools"`.

```suggestion
  "categories": [
    "Fun"
  ],
```

**Rule Used:** What: Assign at least one predefined category to e... ([source](https://app.greptile.com/review/custom-context?memory=f49debbf-b6f6-4c0d-9b35-e1927815992b))

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: extensions/morse-code-reader/src/morse-code-reader.tsx
Line: 155-160

Comment:
**Output field accepts user edits that are silently discarded**

The output `Form.TextArea` uses `onChange={() => {}}` to appear read-only, but users can still click into it and type — their input is just silently dropped. Consider using `Form.Description` for a truly non-interactive display, which is also the semantically correct component for showing computed output.

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: extensions/morse-code-reader/CHANGELOG.md
Line: 1-3

Comment:
**Informal changelog title and non-standard release label**

The file title `# Learning Changelog` appears to be a personal note rather than the standard format. The release label `[Initial Version]` also deviates from the conventional `[Initial Release]` used across extensions in this repo.

```suggestion
# Morse Code Reader Changelog

## [Initial Release] - {PR_MERGE_DATE}
```

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "first commit" | Re-trigger Greptile}

[greptile-apps]

Unused dependency: @raycast/utils

@raycast/utils is declared as a dependency but is never imported in src/morse-code-reader.tsx (the only source file). This bloats the bundle unnecessarily.

Suggested change

	"@raycast/api": "^1.104.13",
	"@raycast/utils": "^1.17.0"
	"@raycast/api": "^1.104.13"

Rule Used: What: Every dependency listed in package.json must... (source)

Prompt To Fix With AI

This is a comment left during a code review.
Path: extensions/morse-code-reader/package.json
Line: 25-26

Comment:
**Unused dependency: `@raycast/utils`**

`@raycast/utils` is declared as a dependency but is never imported in `src/morse-code-reader.tsx` (the only source file). This bloats the bundle unnecessarily.

```suggestion
    "@raycast/api": "^1.104.13"
```

**Rule Used:** What: Every dependency listed in package.json must... ([source](https://app.greptile.com/review/custom-context?memory=bffc60eb-f9f2-4219-b804-76e29e267d43))

How can I resolve this? If you propose a fix, please make it concise.

[greptile-apps]

Missing metadata/ folder with store screenshots

The command uses "mode": "view", so Raycast Store guidelines require a metadata/ folder containing at least one Raycast-styled screenshot. Without it, the extension cannot be published to the store. See the screenshots docs for the required format.

Rule Used: What: Extensions with view-type commands must incl... (source)

Prompt To Fix With AI

This is a comment left during a code review.
Path: extensions/morse-code-reader/package.json
Line: 21-23

Comment:
**Missing `metadata/` folder with store screenshots**

The command uses `"mode": "view"`, so Raycast Store guidelines require a `metadata/` folder containing at least one Raycast-styled screenshot. Without it, the extension cannot be published to the store. See the [screenshots docs](https://developers.raycast.com/basics/prepare-an-extension-for-store#screenshots) for the required format.

**Rule Used:** What: Extensions with view-type commands must incl... ([source](https://app.greptile.com/review/custom-context?memory=87059ac1-c601-487f-9f1c-bce8a3cb6209))

How can I resolve this? If you propose a fix, please make it concise.

[greptile-apps]

Incorrect category for a Morse Code extension

"Security" is reserved for extensions like password managers and secrets tools. A Morse Code translator fits "Fun" (novelty/entertainment tool) or possibly "Developer Tools".

Suggested change

	"categories": [
	"Security"
	],
	"categories": [
	"Fun"
	],

Rule Used: What: Assign at least one predefined category to e... (source)

Prompt To Fix With AI

This is a comment left during a code review.
Path: extensions/morse-code-reader/package.json
Line: 12-14

Comment:
**Incorrect category for a Morse Code extension**

`"Security"` is reserved for extensions like password managers and secrets tools. A Morse Code translator fits `"Fun"` (novelty/entertainment tool) or possibly `"Developer Tools"`.

```suggestion
  "categories": [
    "Fun"
  ],
```

**Rule Used:** What: Assign at least one predefined category to e... ([source](https://app.greptile.com/review/custom-context?memory=f49debbf-b6f6-4c0d-9b35-e1927815992b))

How can I resolve this? If you propose a fix, please make it concise.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[greptile-apps]

Output field accepts user edits that are silently discarded

The output Form.TextArea uses onChange={() => {}} to appear read-only, but users can still click into it and type — their input is just silently dropped. Consider using Form.Description for a truly non-interactive display, which is also the semantically correct component for showing computed output.

Prompt To Fix With AI

This is a comment left during a code review.
Path: extensions/morse-code-reader/src/morse-code-reader.tsx
Line: 155-160

Comment:
**Output field accepts user edits that are silently discarded**

The output `Form.TextArea` uses `onChange={() => {}}` to appear read-only, but users can still click into it and type — their input is just silently dropped. Consider using `Form.Description` for a truly non-interactive display, which is also the semantically correct component for showing computed output.

How can I resolve this? If you propose a fix, please make it concise.