npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

ksdocs

v1.1.3

Published

Document Engine

Downloads

101

Readme

KsDoc library series version 1.X.X

KsDoc is a versatile library within the Ksike ecosystem, designed to streamline and simplify the documentation process for various application types, including CLI, web, and API development. This library integrates seamlessly with Swagger and JSDoc, harnessing their combined power to provide comprehensive and intuitive documentation.

  • Unified Documentation: KsDoc unifies the documentation process, catering to the diverse needs of CLI, web, and API applications.

  • Intuitive Documentation Generation: The library simplifies the generation of documentation, making it an intuitive process for developers.

  • Swagger Integration: Seamless integration with Swagger ensures that APIs are well-documented, conforming to industry standards.

  • JSDoc Integration: By leveraging JSDoc, KsDoc enhances code documentation, ensuring clarity and consistency in the codebase.

  • Multi-Area Support: KsDoc supports documentation across various areas, providing a holistic solution for different application domains.

This library belong to the Ksike ecosystem:

  • KsMf - Microframework (WEB, REST API, CLI, Proxy, etc)
  • Ksdp - Design Patterns Library (GoF, GRASP, IoC, DI, etc)
  • KsCryp - Cryptographic Library (RSA, JWT, x509, HEX, Base64, Hash, etc)
  • KsHook - Event Driven Library
  • KsEval - Expression Evaluator Library
  • KsWC - Web API deployment Library
  • KsTpl - Template Engine
  • KsDoc - Document Engine

KsDoc stands out as a valuable addition to the Ksike ecosystem, offering developers an efficient and unified solution for documentation needs across diverse application types. With support for CLI, web, and API documentation, seamless integration with Swagger and JSDoc, and an emphasis on intuitive processes, KsDoc empowers developers to create well-documented and user-friendly applications.

Quick overview

  • Server file:
const express = require("express");
const ksdocs = require("ksdocs");

const app = express();

ksdocs.inject({
    path: {
      ...ksdocs.path,
      root: __dirname + "/docs"
    },
}).init(app, express.static);

app.listen(5555);

Through the configuration file it is possible to redefine all the behavior of the library as:

  • Paths: The hierarchical path system to use, allowing to have access to the lib resource, local resource and schema resources.
  • Templates: The template list to be used.
  • Routes: Public URLs to be used.
  • Scope: It is only rendered public scope, by default it is public.
  • Services and Controllers:
    • languageService: Defines how to get the language data to support multilanguage.
    • dataService: Defines how to get the data content to fill the templates.
    • menuService: Defines how to load the main menu.
    • tplService: Defines the demplate engine management. By default it is an KsTpl instance.
    • logger: Log managements
    • sessionService: Defines how to maintain and store the user session required for authentication and security, if set to null there is no security
    • authService: Defines how to check the user which is trying to login and generate access token.
    • apiController: By default it use Swagger integration

Optional Config file in JSON format

File: <PATH_DOC>/<SCHEMA_NAME>/_/config.json

{
  "cfg": {
    "scope": "public",
    "menu": [
      { "name": "Introduction", "url": "{root}/{schema}/{page}" },
      { "name": "Onboarding" }
    ]
  },
  "path": {
    "api": "{root}/{schema}/api",
    "page": "{root}/{schema}/page",
    "lang": "{root}/{schema}/lang",
    "config": "{root}/{schema}/config",
    "resource": "{root}/{schema}/resource",
    "core": "{root}/{schema}/_",
    "cache": "{core}/cache"
  },
  "route": {
    "resource": "/resource",
    "login": "{root}/auth/login",
    "logout": "{root}/auth/logout",
    "access": "{root}/auth/access",
    "unauthorized": "{root}/auth/access",
    "public": "{resource}/{schema}",
    "home": "{root}/{schema}",
    "pag": "{root}/{schema}/{page}",
    "api": "{root}/{schema}/api",
    "src": "{root}/{schema}/src"
  },
  "template": {
	  "layout": "{lib}/template/page.layout.html"
  },
  "apiController": null
}

Optional Config file in JavaScript format:

File: <PATH_DOC>/<SCHEMA_NAME>/_/config.js

module.exports = {
  "cfg": {
    "scope": "public"
  },
  "path": {
    "api": "{root}/{schema}/api",
    "page": "{root}/{schema}/page",
    "lang": "{root}/{schema}/lang",
    "config": "{root}/{schema}/config",
    "resource": "{root}/{schema}/resource",
    "core": "{root}/{schema}/_",
    "cache": "{core}/cache"
  },
  "route": {
    "resource": "/resource",
    "login": "{root}/auth/login",
    "logout": "{root}/auth/logout",
    "access": "{root}/auth/access",
    "unauthorized": "{root}/auth/access",
    "public": "{resource}/{schema}",
    "home": "{root}/{schema}",
    "pag": "{root}/{schema}/{page}",
    "api": "{root}/{schema}/api",
    "src": "{root}/{schema}/src"
  },
  "template": {
	 "layout": "{core}/template/page.layout.html"
  },
  apiController: null,
  languageService: {
    load: ({ path, idiom = "en" }) => Promise.resolve(require(path + "/" + idiom + ".json"))
  },
  logger: console
}