your-library throws TypeError on Node 22
After upgrading to Node 22 my build fails with TypeError: Cannot read properties of undefined. The stack trace points at your-library/dist/index.js line 42. Works fine on Node 20.
first set, phase 1b
Questions, answers, and comments across the Stack Exchange network, including Stack Overflow, through the official API. Zero vendor pages exist for this query today.
Name stackexchange as the source in a search or catch. discatch reads questions, answers, and comments across the Stack Exchange network through the official API. Stack Overflow is the largest site in the network. Score, answer count, and view count on each result feed the prescore. Use site: in the query to restrict to one site.
Questions, answers, and comments that mention your product, library, or topic, with score, answer count, and view count on each result. Covers Stack Overflow and the rest of the Stack Exchange network.
The official Stack Exchange API, free within its quota. Tags, site, and time filters map through; results are re-filtered locally against your full query.
One syntax for every source: quotes, AND, OR, NOT, site:, author:, lang:.
query
"your-library" AND (error OR "how to")One result, as a catch delivers it: source, author, the post, a prescore, thread context, and a suggested action your agent can act on.
After upgrading to Node 22 my build fails with TypeError: Cannot read properties of undefined. The stack trace points at your-library/dist/index.js line 42. Works fine on Node 20.
The query people type is "Stack Overflow keyword alerts." The page title and slug say Stack Overflow because that is what searchers look for. The source covers the full Stack Exchange network, with Stack Overflow as the largest site. The source ID in the API is stackexchange.
Stack Overflow’s voting system is the strongest signal in the prescore for this source. A question with five upvotes and zero answers is a gap. A question with zero upvotes and three downvotes is noise. The engagement signal in the prescore maps directly to Stack Overflow’s score field.
Zero listening-vendor pages exist for "Stack Overflow keyword alerts." Wikipedia ranks number one. The rest of the results are a PyPI package, a Medium DIY post, and GitHub repos. On the "monitor Stack Overflow for mentions" phrasing, half the results are about Stack Overflow’s own infrastructure monitoring. Only Noisely and Mentio have tool pages, and neither pushes to an agent.
For DevRel and developer-tools teams, Stack Overflow is where users go when the docs fail them. An unanswered question about your library is a gap. A comparison answer that gets the facts wrong about your product is a correction waiting to happen. A catch at one hour finds both before they go stale.
Errors mentioning your library
"your-library" AND (error OR TypeError OR "does not work")Comparison questions
"your-product" AND ("vs" OR "alternative" OR "compared to")Specific Stack Exchange site
site:webmasters.stackexchange.com "brand mention alerts"A catch on your library name at one hour finds unanswered questions before they go stale. An unanswered question with two upvotes is a support gap. An accepted answer that recommends a competitor is a positioning signal. The reply-draft playbook helps your team draft answers in your voice: answer the question first, mention the product once, never in the first sentence.
Stack Overflow answers rank in search. A correct answer to a comparison question with your product’s name in it will rank for the same query the questioner typed. This makes Stack Overflow answers a durable surface, not a one-time reply.
Stack Overflow is the largest site, but the network has over 170 sites. Webmasters Stack Exchange carries questions about brand monitoring tools. Server Fault carries questions about monitoring infrastructure. Software Recommendations carries questions where people ask for tools. Use site: in the query to restrict to one site, or leave it out to search all of them.
Score and answer count on each result feed the prescore. A question with zero answers and a positive score is a gap. A question with a negative score is noise. The prescore filters so your agent sees the gaps first.
Not yet. Stack Overflow is in the first set of sources, phase 1b of the roadmap, and discatch is pre-launch. The API serves the doctor manifest today, and the manifest’s sources_now list is the truth for what is live. When phase 1b ships, catches on this source read Stack Overflow through the official Stack Exchange API with no provider in the middle.
The full Stack Exchange network, with Stack Overflow the largest. Use site: in the query to restrict to one site, or leave it out to search all of them.
One search unit per call, plus one result unit per matched item. The quote tells you the ceiling. Free-source searches cost less than waterfall searches.
Both questions and answers, plus comments. A mention in an answer is a result with the question URL as parent_url.
Yes. Use your library name in quotes as the query. Add tags like [python] or [javascript] if you want to narrow by technology.
A catch on your product name at one hour finds unanswered questions before they go stale. The reply-draft playbook helps your team draft answers in your voice.
The official API has a daily quota. discatch prices quota usage into the quote. If the quota is tight, the quote says so and the call costs more.
Almost none. Wikipedia ranks number one for "Stack Overflow keyword alerts." Noisely and Mentio have tool pages on the "mentions" phrasing. No other listening vendor has a dedicated Stack Overflow page.
Yes. Use site: in the query, for example site:serverfault.com or site:superuser.com.
No. discatch never posts. The reply-draft playbook helps your own agent draft an answer for you to review and post.
Yes. Name both sources in the catch. A catch on your library name across stackexchange and github finds questions on Stack Overflow and issues on GitHub, delivered to the same destination. Results carry the source field so you know where each came from.
Last reviewed by Parsa Khazaeepoul, founder, dcouple. Facts from docs/data-sources.md and docs/coverage-matrix.md; status from docs/api.md; the search landscape from docs/seo/keyword-map.md.