TypeScript still can't type thrown errors even with @throws JSDoc, so your catch blocks remain `unknown`—but there's a pattern emerging in 2026 that actually works without waiting for the language.
#TypeScript #JavaScript #WebDev #Programming #Coding
#TypeScript #JavaScript #WebDev #Programming #Coding
https://medium.com/@jsmanifest/22dbadba5a6e
medium.com
November 3, 2026 at 6:06 AM
TypeScript still can't type thrown errors even with @throws JSDoc, so your catch blocks remain `unknown`—but there's a pattern emerging in 2026 that actually works without waiting for the language.
#TypeScript #JavaScript #WebDev #Programming #Coding
#TypeScript #JavaScript #WebDev #Programming #Coding
maybe insane question: is there a way to get jsdoc coverage
October 28, 2026 at 8:13 PM
maybe insane question: is there a way to get jsdoc coverage
i am doing some things incredibly wrong:
1. "Typescript" but it's just JSDoc comments but it still reports errors with `tsc`
2. on a custom Javascript runtime (BoaJS + my incremental extensions, also typed)
3. with absolutely no third-party JS packages (i wrote a small templating library […]
1. "Typescript" but it's just JSDoc comments but it still reports errors with `tsc`
2. on a custom Javascript runtime (BoaJS + my incremental extensions, also typed)
3. with absolutely no third-party JS packages (i wrote a small templating library […]
Original post on social.treehouse.systems
social.treehouse.systems
October 22, 2026 at 1:51 AM
i am doing some things incredibly wrong:
1. "Typescript" but it's just JSDoc comments but it still reports errors with `tsc`
2. on a custom Javascript runtime (BoaJS + my incremental extensions, also typed)
3. with absolutely no third-party JS packages (i wrote a small templating library […]
1. "Typescript" but it's just JSDoc comments but it still reports errors with `tsc`
2. on a custom Javascript runtime (BoaJS + my incremental extensions, also typed)
3. with absolutely no third-party JS packages (i wrote a small templating library […]
writing an XML-doc or JSDoc and having it show up over code elsewhere (just one example) simply isn't the same thing as some smartass bot misgender you and proceed to implement your change request incorrectly (actual fucking thing that's happened while a coworker was screensharing their setup btw)
October 7, 2026 at 12:59 AM
writing an XML-doc or JSDoc and having it show up over code elsewhere (just one example) simply isn't the same thing as some smartass bot misgender you and proceed to implement your change request incorrectly (actual fucking thing that's happened while a coworker was screensharing their setup btw)
Update dependency eslint-plugin-jsdoc to v65 (renovate[bot])
https://github.com/mastodon/mastodon/pull/40817
https://github.com/mastodon/mastodon/pull/40817
Update dependency eslint-plugin-jsdoc to v65 by renovate[bot] · Pull Request #40817 · mastodon/mastodon
This PR contains the following updates: Package Change Age Confidence eslint-plugin-jsdoc 64.5.4 → 65.0.1 WarningSome dependencies could not be looked up. Check the Dependency Dashboar...
github.com
October 5, 2026 at 9:16 AM
Update dependency eslint-plugin-jsdoc to v65 (renovate[bot])
https://github.com/mastodon/mastodon/pull/40817
https://github.com/mastodon/mastodon/pull/40817
The most underrated AI coding workflow: let it refactor the boring file nobody wants to touch. Strict TypeScript + JSDoc in one pass. Ship it.
October 1, 2026 at 10:00 PM
The most underrated AI coding workflow: let it refactor the boring file nobody wants to touch. Strict TypeScript + JSDoc in one pass. Ship it.
This is what I meant. You see the JSDoc text even though you didn't create it through a function declaration and didn't annotate the var itself
September 23, 2026 at 10:56 AM
This is what I meant. You see the JSDoc text even though you didn't create it through a function declaration and didn't annotate the var itself
"I can just jsdoc my js" is literally what I was doing for a long time, and it's why I mostly gave up on type script. Not worth it. But we did a pretty heavy redesign of a project so I converted it, and wow. But no way I could have figured it out without an LLM.
September 20, 2026 at 3:22 PM
"I can just jsdoc my js" is literally what I was doing for a long time, and it's why I mostly gave up on type script. Not worth it. But we did a pretty heavy redesign of a project so I converted it, and wow. But no way I could have figured it out without an LLM.
I still tell it to put JSDoc comments in my JavaScript and let VSCode's built-in TypeScript check for problems, but I'm not really sure if it matters; even when I'm using a harness outside of VSCode it they don't create any type errors.
What do you find useful about it?
What do you find useful about it?
September 20, 2026 at 2:23 PM
I still tell it to put JSDoc comments in my JavaScript and let VSCode's built-in TypeScript check for problems, but I'm not really sure if it matters; even when I'm using a harness outside of VSCode it they don't create any type errors.
What do you find useful about it?
What do you find useful about it?
We recently switched to auto-generating the reference docs from jsdoc comments. This has multiple advantages:
- can't get out of sync
- gives you suggestions in code
I'll see if we can make the rendered output better though, thanks for the feedback 🙏
- can't get out of sync
- gives you suggestions in code
I'll see if we can make the rendered output better though, thanks for the feedback 🙏
September 17, 2026 at 6:15 PM
We recently switched to auto-generating the reference docs from jsdoc comments. This has multiple advantages:
- can't get out of sync
- gives you suggestions in code
I'll see if we can make the rendered output better though, thanks for the feedback 🙏
- can't get out of sync
- gives you suggestions in code
I'll see if we can make the rendered output better though, thanks for the feedback 🙏
En esa realidad probablemente seguiríamos debatiendo si usar #ifdef o JSDoc para tipos, con el mismo resultado: la mitad del equipo ignorándolo. Curioso que muchos proyectos en JS puro terminan reinventando validación de tipos en runtime de todos modos.
September 13, 2026 at 11:12 AM
En esa realidad probablemente seguiríamos debatiendo si usar #ifdef o JSDoc para tipos, con el mismo resultado: la mitad del equipo ignorándolo. Curioso que muchos proyectos en JS puro terminan reinventando validación de tipos en runtime de todos modos.
And it types them perfectly with JSDoc based typing
September 10, 2026 at 1:15 PM
And it types them perfectly with JSDoc based typing
感覺現在最大問題是1作品集都沒公開2沒有長期維護經驗，甚至沒有標準除錯流程3沒有團隊協作經驗
還有個隱藏款：c程式碼沒有固定的架構（頂多就是順手寫個JSDoc，雖然對如果只有自己維護+給使用者API介面，這樣就差不多了，但還是進步了業界）
還有個隱藏款：c程式碼沒有固定的架構（頂多就是順手寫個JSDoc，雖然對如果只有自己維護+給使用者API介面，這樣就差不多了，但還是進步了業界）
September 10, 2026 at 2:40 AM
感覺現在最大問題是1作品集都沒公開2沒有長期維護經驗，甚至沒有標準除錯流程3沒有團隊協作經驗
還有個隱藏款：c程式碼沒有固定的架構（頂多就是順手寫個JSDoc，雖然對如果只有自己維護+給使用者API介面，這樣就差不多了，但還是進步了業界）
還有個隱藏款：c程式碼沒有固定的架構（頂多就是順手寫個JSDoc，雖然對如果只有自己維護+給使用者API介面，這樣就差不多了，但還是進步了業界）
And then you discover a trick to preserve the attachment of JSDoc to a function signature: you need to declare the function signature as a fucking
interface FunName {
/*
* @param arg1
/*
(arg1:type): returnType
}
And when you return this interface from anywhere, the JSDoc comment will show
interface FunName {
/*
* @param arg1
/*
(arg1:type): returnType
}
And when you return this interface from anywhere, the JSDoc comment will show
September 8, 2026 at 7:32 PM
And then you discover a trick to preserve the attachment of JSDoc to a function signature: you need to declare the function signature as a fucking
interface FunName {
/*
* @param arg1
/*
(arg1:type): returnType
}
And when you return this interface from anywhere, the JSDoc comment will show
interface FunName {
/*
* @param arg1
/*
(arg1:type): returnType
}
And when you return this interface from anywhere, the JSDoc comment will show
At least when there's no documentation somebody will help you figure it out rather than going "umm check confluence"
Godd the jsdoc situation is always a mess with claude
Godd the jsdoc situation is always a mess with claude
September 8, 2026 at 12:06 PM
At least when there's no documentation somebody will help you figure it out rather than going "umm check confluence"
Godd the jsdoc situation is always a mess with claude
Godd the jsdoc situation is always a mess with claude
Can characters be escaped in code blocks in JSDoc comments?
I want something like this:
/**
* ```js
* /* This is a comment inside a code block inside a comment */
* ```
*/
It only has to work for TypeScript, not every JSDoc tool out there.
I want something like this:
/**
* ```js
* /* This is a comment inside a code block inside a comment */
* ```
*/
It only has to work for TypeScript, not every JSDoc tool out there.
September 7, 2026 at 1:52 PM
Can characters be escaped in code blocks in JSDoc comments?
I want something like this:
/**
* ```js
* /* This is a comment inside a code block inside a comment */
* ```
*/
It only has to work for TypeScript, not every JSDoc tool out there.
I want something like this:
/**
* ```js
* /* This is a comment inside a code block inside a comment */
* ```
*/
It only has to work for TypeScript, not every JSDoc tool out there.
I want to use this for css-modules-content-mapper, which shows CSS previews. I already strip comments, but people might write something like:
.doc:after {
content: '*/';
}
I don’t want that to break the JSDoc comment it will be embedded inside of.
.doc:after {
content: '*/';
}
I don’t want that to break the JSDoc comment it will be embedded inside of.
September 7, 2026 at 4:24 PM
I want to use this for css-modules-content-mapper, which shows CSS previews. I already strip comments, but people might write something like:
.doc:after {
content: '*/';
}
I don’t want that to break the JSDoc comment it will be embedded inside of.
.doc:after {
content: '*/';
}
I don’t want that to break the JSDoc comment it will be embedded inside of.
I Created
Go To Definition for JSDoc — jump to {@link} symbols in VS Code without adding throwaway imports. laststance.io/articles/Go-...
Go To Definition for JSDoc — jump to {@link} symbols in VS Code without adding throwaway imports. laststance.io/articles/Go-...
Go To Definition for JSDoc: symbol jumps without throwaway imports
A small VS Code extension for jumping from JSDoc {@link SymbolName} references to TypeScript workspace symbols without adding imports just for navigation.
laststance.io
September 7, 2026 at 3:34 AM
I Created
Go To Definition for JSDoc — jump to {@link} symbols in VS Code without adding throwaway imports. laststance.io/articles/Go-...
Go To Definition for JSDoc — jump to {@link} symbols in VS Code without adding throwaway imports. laststance.io/articles/Go-...
📢 We have mostly moved the TanStack Query API reference docs to being auto-generated from JsDoc comments.
This might mean some of the pages will temporarily have less information than before.
If you see something that doesn't look right, please reach out and/or file a PR 🙏
This might mean some of the pages will temporarily have less information than before.
If you see something that doesn't look right, please reach out and/or file a PR 🙏
@tanstack/react-query | TanStack Query React Docs
Interfaces Type Aliases Variables Functions
tanstack.com
September 6, 2026 at 3:35 PM
📢 We have mostly moved the TanStack Query API reference docs to being auto-generated from JsDoc comments.
This might mean some of the pages will temporarily have less information than before.
If you see something that doesn't look right, please reach out and/or file a PR 🙏
This might mean some of the pages will temporarily have less information than before.
If you see something that doesn't look right, please reach out and/or file a PR 🙏
The @svelte.dev team has ignored a regression for 10 days now. Have to pin esrap to 2.3.4; otherwise, builds will fail as they re-introduced the regression in 2.3.5 😐
JSDoc type-cast parentheses applied to function parameters produce invalid output (`(row) = fallback`) — regression in 2.3.3 · Issue #181 · sveltejs/esrap
Since 2.3.3 (fix: preserve parantheses of jsdoc type casts, 3cbb677), the cast-parenthesization can fire on the left side of an AssignmentPattern in a function parameter list, where the parentheses...
github.com
September 4, 2026 at 7:31 AM
The @svelte.dev team has ignored a regression for 10 days now. Have to pin esrap to 2.3.4; otherwise, builds will fail as they re-introduced the regression in 2.3.5 😐
It appears that @zed.dev does not support @augments or @extends in jsdoc. Can anyone confirm/deny?
I have a typedef for a subset of properties. I want to create another typedef for those properties plus others. Zed insists on giving it an 'any' type, apparently? Or I am doing something wrong?
I have a typedef for a subset of properties. I want to create another typedef for those properties plus others. Zed insists on giving it an 'any' type, apparently? Or I am doing something wrong?
September 1, 2026 at 8:02 PM
It appears that @zed.dev does not support @augments or @extends in jsdoc. Can anyone confirm/deny?
I have a typedef for a subset of properties. I want to create another typedef for those properties plus others. Zed insists on giving it an 'any' type, apparently? Or I am doing something wrong?
I have a typedef for a subset of properties. I want to create another typedef for those properties plus others. Zed insists on giving it an 'any' type, apparently? Or I am doing something wrong?
There are also incredible tools out there to automate custom element types.
Check out @stuffbreaker.bsky.social's WC Toolkit that can take no-build JSDoc annotations (or TypeScript types) to output type defs in the form of Custom Elements Manifest which has support in various IDEs:
wc-toolkit.com
Check out @stuffbreaker.bsky.social's WC Toolkit that can take no-build JSDoc annotations (or TypeScript types) to output type defs in the form of Custom Elements Manifest which has support in various IDEs:
wc-toolkit.com
Web Components Toolkit
Tools for building your next web component library.
wc-toolkit.com
August 31, 2026 at 5:39 PM
There are also incredible tools out there to automate custom element types.
Check out @stuffbreaker.bsky.social's WC Toolkit that can take no-build JSDoc annotations (or TypeScript types) to output type defs in the form of Custom Elements Manifest which has support in various IDEs:
wc-toolkit.com
Check out @stuffbreaker.bsky.social's WC Toolkit that can take no-build JSDoc annotations (or TypeScript types) to output type defs in the form of Custom Elements Manifest which has support in various IDEs:
wc-toolkit.com
Curious where you noticed the pros of jsdoc and the cons of TS? I never fully moved over to ts, but been considering it lately, so those would be very interesting
August 21, 2026 at 6:08 AM
Curious where you noticed the pros of jsdoc and the cons of TS? I never fully moved over to ts, but been considering it lately, so those would be very interesting
Types are still there, they just get out of my way and I am not forced to insert build steps if I don’t want them.
The TS lang server is where the value resides and it is perfectly capable of consuming standard JSDoc type comments.
The TS lang server is where the value resides and it is perfectly capable of consuming standard JSDoc type comments.
August 20, 2026 at 9:41 PM
Types are still there, they just get out of my way and I am not forced to insert build steps if I don’t want them.
The TS lang server is where the value resides and it is perfectly capable of consuming standard JSDoc type comments.
The TS lang server is where the value resides and it is perfectly capable of consuming standard JSDoc type comments.
It's still incredibly pleasing to run through old projects converting TS into JS + JSDoc.
I made the decision to cut out TS (excluding `.d.ts` files, they get a pass) from all my personal projects years ago and I'm still very much convinced that's the right move. TS as an authoring format ain't it.
I made the decision to cut out TS (excluding `.d.ts` files, they get a pass) from all my personal projects years ago and I'm still very much convinced that's the right move. TS as an authoring format ain't it.
August 20, 2026 at 4:55 AM
It's still incredibly pleasing to run through old projects converting TS into JS + JSDoc.
I made the decision to cut out TS (excluding `.d.ts` files, they get a pass) from all my personal projects years ago and I'm still very much convinced that's the right move. TS as an authoring format ain't it.
I made the decision to cut out TS (excluding `.d.ts` files, they get a pass) from all my personal projects years ago and I'm still very much convinced that's the right move. TS as an authoring format ain't it.