This package provides a programmatic way to access documentation URLs for JavaScript global objects across various environments including built-in types, non-standard APIs, and browser, worker, or Node.js specific globals. It exposes a `docs` object containing all categorized links and a `getDoc` function to retrieve a specific URL by name. The current stable version is 2.4.1, which was last published over seven years ago (as of April 2026). Crucially, the GitHub repository for this project has been archived, indicating that the package is no longer maintained and is considered abandoned. Users should be aware that the documentation links provided by this package are highly likely to be outdated and may no longer resolve correctly due to changes on the target documentation sites (e.g., MDN/Mozilla Developer Center).
npm install globals-docsVerified import paths — ran on the pinned version, not inferred.
This quickstart demonstrates how to use `getDoc` to retrieve specific global documentation URLs and how to access the raw `docs` object to explore available documentation categories and links. It highlights CommonJS usage.
Consider alternatives that provide up-to-date documentation links or directly reference current MDN/developer resources.
Always verify retrieved URLs manually before relying on them. For current documentation, prefer direct searches on MDN Web Docs or other official sources.
Use CommonJS `const { symbol } = require('globals-docs');` syntax. If you absolutely need ESM, ensure your bundler properly handles CJS interoperability.For modern JavaScript features, rely on contemporary documentation sources. This package is only useful for historically stable, older APIs.
Ensure you are using CommonJS `const { getDoc } = require('globals-docs');`. If the symbol itself is truly missing, check the package's exports.While `globals-docs` is CJS, if you encounter this, it points to a broader module interoperability issue in your project. Ensure your Node.js version and project configuration support CJS `require` calls from your ESM code, or stick to CJS for projects using `globals-docs`.
Verify the spelling of the global object name. Be aware that the package is outdated and may not contain links for all existing or newly introduced globals.
No dependency data recorded yet.