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

@quodatum/xq-catalogs

v0.1.2

Published

XQuery namespace and module library definitions as JSON

Downloads

13

Readme

@quodatum/xq-catalogs

github

XQuery namespace and module library definitions as JSON.

npm

API

profiles()

returns array of Profiles defined in profiles.json.

[
   {
      "id": "basex-10",
      "description": "BaseX 10.6 features",
      "modules": [
         "packages/basex-static-namespaces.json",
         "packages/xpath-3.1.json",
         "packages/basex-10.6.json"
      ]
   },
   {
      "id": "basex-9",
      "description": "BaseX 9.7 features",
      "modules": [
         "packages/basex-static-namespaces.json",
         "packages/xpath-3.1.json",
         "packages/basex-9.7.json"
      ]
   },
  ...
]

library(profile)

returns object describing namespaces and modules available for processor

This is the xqdoc like format where var/fns are objects. Format subject to change, something like..

"http://basex.org": {
        "description": "BaseX Annotations, Pragmas, …",
        "prefixes": [
            "basex"
        ],
        "type": "declare"
    },
...
"http://basex.org/modules/admin": {
  "ns": "http://basex.org/modules/admin",
  "prefixes": [
   "admin"
  ],
  "namespaces": [],
  "variables": {},
  "functions": {
   "http://basex.org/modules/admin#logs#0": {
    "name": "logs",
    "uri": "http://basex.org/modules/admin",
    "key": "http://basex.org/modules/admin#logs#0",
    "params": [],
    "type": "element(file)*",
    "description": " Returns <a href=\"https://web.archive.org/web/20220623230943/https://docs.basex.org/web/20220623231027/https://docs.basex.org/wiki/Logging\">Logging</a> data compiled by the database or HTTP server: <ul> <li>If no argument is specified, a list of all log files will be returned, including the file size and date.</li> <li>If a <code>$date</code> is specified, the contents of a single log file will be returned.</li> <li>If <code>$merge</code> is set to true, related log entries will be merged. Please note that the merge might not be 100% successful, as log entries may be ambiguous.</li> </ul>"
   },

Dev notes

index.ts is source. tsc is used to compile to into a "commonjs" module for now.

sources files

The npm script wiki-scrape creates stub xqm files below packages.src from the BaseX wiki.