Dev
JavaScript Module Generator
A new JavaScript file too often starts blank, with no documentation and an implicit default export. This tool generates an ES module skeleton with named exports and JSDoc so the file starts with structure and your editor has enough information to offer autocompletion. Name the module by its purpose — for example, `userService` — and list the functions to export, separated by commas. Names are normalised to camelCase. The output includes a module-level JSDoc header with `@module`, then one `export async function` per name with `@param {object} options`, `@returns {Promise<unknown>}`, and a `throw new Error("not implemented")` body. Paste the skeleton into a `.js` or `.mjs` file, implement each function, and refine the JSDoc types. The `throw` stubs are intentional: a half-finished module that fails loudly when called is far easier to debug than one that silently returns `undefined`.
How to use
- Choose your options above
- Click Generate
- Copy your result
Detailed instructions
- Name the module by its purpose.
- List the functions to export, separated by commas.
- Click Generate to build the module skeleton.
- Paste it into a .js or .mjs file and implement each function.
Use Cases
- •Scaffolding a new service or utility module
- •Keeping named-export style consistent across a project
- •Remembering the JSDoc shape for editor autocompletion
- •Stubbing functions that fail loudly until implemented
- •Teaching ES module structure to newer developers
Tips
- →Use named exports so consumers import exactly what they need.
- →Refine the JSDoc param and return types for better autocompletion.
- →Drop async on any function that is purely synchronous.
- →Keep one clear responsibility per module.
FAQ
why do the stubs throw instead of returning undefined
A function that throws `"not implemented"` fails the moment it is called, making an incomplete module immediately visible. Returning `undefined` silently propagates a confusing bug downstream — the throw prevents that.
why are the functions async by default
Service and I/O functions almost always end up async. Defaulting to `async` and a `Promise<unknown>` return type saves a step for the common case. Remove `async` and update the JSDoc for any function that is purely synchronous.
how does the generator clean up function names
Each name is converted to camelCase and stripped of invalid identifier characters, so inputs in snake_case, kebab-case, or with spaces all produce valid, consistently formatted function names.
You might also like
Popular tools from other categories that share themes with this one.
Try these next
More free tools from other corners of the catalog, picked by shared themes.