(Ten years later.) There are two parts to your question:
Seeing documentation for methods and such from the standard library.
Yes, most modern JavaScript IDEs (like Visual Studio Code, WebStorm, ...) have documentation for the JavaScript standard library objects/methods built into them (usually by drawing on the type information from definitely typed, which also includes types for lots of other libraries you may use).
Including documentation in your own code and seeing it / building documentation files.
Yes, most modern JavaScript IDEs support JSDoc (which is very JavaDoc-like) and will show you your documentation inline.
To actually build documentation, you'll need a tool that understands JSDoc (whether it's the JSDoc tool itself or any of several others that also understand the format) that creates documentation files for you in HTML, PDF, or whatever format.
Here are some examples of JSDoc comments (taken from my answer here), but see the JSDoc documentation for details:
/**
* Does something nifty.
*
* @param whatsit The whatsit to use (or whatever).
* @returns A useful value.
*/
function nifty(whatsit) {
return /*...*/;
}
You can augment that with types if you want type hints:
/**
* Does something nifty.
*
* @param {number} whatsit The whatsit to use (or whatever).
* @returns {string} A useful value.
*/
function nifty(whatsit) {
return /*...*/;
}
If you use TypeScript, the types would be part of the code rather than in the JSDoc:
// TypeScript example
/**
* Does something nifty.
*
* @param whatsit The whatsit to use (or whatever).
* @returns A useful value.
*/
function nifty(whatsit: number): string {
return /*...*/;
}