Add duden extension

[ahinderling]

Description

Lookup lemma from the online DUDEN (German language dictionary)

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.

[greptile-apps]

Greptile Summary

This PR adds a new Duden (German dictionary) extension that scrapes Duden.de using cheerio, displays word details (part of speech, frequency, meanings, synonyms, etymology, IPA), and uses useNavigation().push() for proper back-navigation. The extension is well-structured with caching, request timeouts, and correct Raycast conventions throughout.

Confidence Score: 5/5

Safe to merge — all remaining findings are P2 style suggestions that do not affect runtime behavior.

Navigation is correctly handled with useNavigation().push(), the frequency display is protected against out-of-range values, the changelog uses the {PR_MERGE_DATE} placeholder, and categories are correctly set to Documentation + Web. The only open finding is the redundant @types/cheerio devDependency, which is a cleanup suggestion and not a blocker.

extensions/duden/package.json — redundant @types/cheerio devDependency

Important Files Changed

Filename	Overview
extensions/duden/src/api/duden.ts	Well-structured API client with request timeout, AbortController, manual TTL-based caching, and correct error handling for 404s.
extensions/duden/src/utils/parser.ts	Solid cheerio-based HTML parser; frequency is extracted via text-length heuristic which is fragile but clamped downstream. Uses cheerio.Cheerio type annotation that relies on the redundant @types/cheerio@0.22.35.
extensions/duden/src/components/WordDetails.tsx	Clean Detail view; frequency is clamped with Math.min/Math.max so repeat() never receives a negative argument. Proper ActionPanel with copy and open-in-browser actions.
extensions/duden/src/search-duden-de.tsx	Uses useNavigation().push() for proper back-navigation; loading state is correctly reset on early-return (< 3 chars); cancellation flag prevents stale state updates.
extensions/duden/package.json	Categories correctly set to Documentation + Web; @types/cheerio is a redundant devDependency that should be removed since cheerio@1.0.0 ships its own types.

Prompt To Fix All With AI

This is a comment left during a code review.
Path: extensions/duden/package.json
Line: 34

Comment:
**`@types/cheerio` is redundant with cheerio@1.0.0**

`cheerio@1.0.0` ships its own bundled TypeScript types; `@types/cheerio@0.22.35` was the DefinitelyTyped package for the old `v0.x` API and is no longer needed. TypeScript prefers a package's own bundled types, so this entry is effectively unused and can cause confusion if the `v0.x` type shapes (e.g. the non-generic `Cheerio` namespace members) differ from what cheerio@1's bundled types export.

```suggestion
    "@types/node": "22.13.10",
```

**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.

_{Reviews (5): Last reviewed commit: "fix stuck loading indicator when search ..." | Re-trigger Greptile}

[raycastbot]

This pull request has been automatically marked as stale because it did not have any recent activity.

It will be closed if no further activity occurs in the next 7 days to keep our backlog clean 😊

[ahinderling]

👋 this is not stale - just waiting for review

[0xdhrv]

Hey @ahinderling 👋

I have added a few comments for you to address.

I'm looking forward to testing this extension again 🔥

Feel free to contact me here or at Slack if you have any questions.

---

I converted this PR into a draft until it's ready for the review, please press the button Ready for review when it's ready and we'll have a look 😊

[0xdhrv]

issue: scraping might violate duden ToS

The extension scrapes Duden.de HTML while impersonating a regular Chrome browser. This is deceptive and may violate Duden.de's Terms of Service.

[0xdhrv]

Hey @ahinderling 👋

I have added a comment for you to address.

I'm looking forward to testing this extension again 🔥

Feel free to contact me here or at Slack if you have any questions.

---

I converted this PR into a draft until it's ready for the review, please press the button Ready for review when it's ready and we'll have a look 😊

[ahinderling]

Hey @0xdhrv 👋 thanks for flagging this.

I've updated the User-Agent in src/api/duden.ts to honestly identify the extension:

Raycast Duden Extension (https://github.com/raycast/extensions)

This removes the "impersonating Chrome" concern — Duden can now recognize the traffic and contact the project or block it if they want.

On the ToS question, I checked both robots.txt and the AGB and couldn't find a violation:

robots.txt (https://www.duden.de/robots.txt)

• /rechtschreibung/* (the path this extension hits) is not disallowed for User-agent: *. Only /suche/, /suchen/, /admin/, /user/, /profiles/, /node, and /filter/tips are blocked.
• AI training crawlers (GPTBot, ClaudeBot, anthropic-ai, CCBot, Bytespider, …) are explicitly blocked site-wide — but this is about bulk training data, not user-initiated lookups.

AGB (https://www.duden.de/service/agb)

• No clause prohibits automated access, scraping, third-party clients, or non-browser user agents.
• § 6 (11) reserves text/data mining rights under § 44b UrhG — this is a blanket reservation against bulk data mining, not individual user queries.
• § 11 (1–3) covers copyright (no redistribution, no removal of notices). The extension doesn't republish content; it displays results to the user who initiated the query, the same as the browser would.

Happy to reconsider if you're aware of a specific clause I missed, or if Raycast has a stricter internal policy for scraping-based extensions. Otherwise I think the honest User-Agent is the right fix here and I'll mark the PR ready for review.

[0xdhrv]

Looks good to me, approved ✅

[github-actions]

Published to the Raycast Store:
https://raycast.com/c76b7srxxm/duden

[raycastbot]

🎉 🎉 🎉

Such a great contribution deserves a reward, but unfortunately we couldn't find your Raycast account based on your GitHub username (@ahinderling).

Please link your GitHub account to your Raycast account to receive your credits and soon be able to exchange them for some swag.