
Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Compiles JSDoc annotated javascript into a Typescript Declaration File (.d.ts).
This library's goal is to be able to take as input a JSDoc annotated source JavaScript file (or many files) and output a single TypeScript Declaration File (.d.ts).
It is distributed as a JSDoc3 template. Running JSDoc with this as the template should result in a TypeScript Definition File.
You can install this module from npm:
$> npm install tsd-jsdoc
To use this module, simply specify it as the template for your normal JSDoc generation.
For example, from the command-line you can do:
$> jsdoc -t node_modules/tsd-jsdoc/dist -r .
Or add this to your JSON configuration:
{
"opts": {
"template": "./node_modules/tsd-jsdoc/dist"
}
}
If you want to use jsdoc/closure tag @template
, you also need to specify this module as a plugin, like so:
{
"plugins": [ "./node_modules/tsd-jsdoc/dist/plugin" ],
"opts": {
"template": "./node_modules/tsd-jsdoc/dist"
}
}
This library provides very little validation beyond what JSDoc provides. Meaning if you have invalid JSDoc comments, this will likely output an invalid TypeScript Definition File.
Additionally there are things that JSDoc allows, that TypeScript does not. This library tries to make these differences transparent, and translate from one to the other when necessary. It can't handle anything though, and you can generate invalid Typescript even if your JSDoc is valid.
JSDoc has a bug that prevents it from
correctly parsing export default class Name {}
. The workaround is to use named exports
(export class Name {}
) or utilize the
jsdoc-export-default-interop plugin.
Tags that describe the code, but support is not implemented are:
@default
- No TS equivalent@deprecated
- No TS equivalent (issue)@event
- No TS equivalent@exports
- Everything is exported@external
- Not sure what behavior would be expected@fires
- No TS equivalent@listens
- No TS equivalent@override
- No TS equivalent (issue)@throws
- No TS equivalentTags that are just metadata and don't actually describe the code are ignored. These are:
@author
@classdesc
@copyright
@description
@example
@file
@license
@requires
@see
@since
@summary
@todo
@tutorial
@version
All other JSDoc tags should work fine.
ClosureCompiler has a couple tags beyond the built-in JSDoc tags that can improve your TypeScript output. Here is a complete list of the tags from CC that are supported in this template:
@template
- For genericsJSDoc doesn't have a way to express all the features of typescript so we treat some syntax as special case to create better Typescript.
Class<T>
- If we encounter a type that is Class<T>
we will treat it as typeof T
. See jsdoc3/jsdoc#1349FAQs
Compiles JSDoc annotated javascript into a Typescript Declaration File (.d.ts).
The npm package tsd-jsdoc receives a total of 598 weekly downloads. As such, tsd-jsdoc popularity was classified as not popular.
We found that tsd-jsdoc demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.