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

@x-dome/xdome-extension-rest

v0.1.4

Published

xdome-extension-rest

Downloads

6

Readme

WIP

Folders Details

  • plugin

    These file are intended to be copied to the project (Just once), and are used by the app (support, templates and others if needed)

    • @TODO -> Make this part of the add endpoint process (CLI)
  • support

    These files are usually extended by the templates, and are the base share logic for this Extension component, it include

    • accessPoint.js: Base logic for route managedment, it include by default:

      • rejects method, base on the non compliance with the allowedVerbs attribute.
        • Post BusinessLogic

      It aslo include the posibility of override the route declaration with routesOverride

    • businessLogic.js: Common logic / process for this endpoint, it include by default:

      • [get|post|put|delete]InputSchemeValidator(data): Intended method for scheme validation (Input data), it will return true by default unlest is overrided. If false it will shortcircuit the process.

        • Pre Endpoint Process
      • [get|post|put|delete]OutputSchemeValidator(data): Intended method for scheme validation (Output data), it will return true by default unlest is overrided. If false it will shortcircuit the process.

        • Post Endpoint Process
      • [get|post|put|delete]InputOverride(data): Intended method for data modification / override (Input data), it also set that information to this.request.dome.input, from where can be used for other methods

        • Pre Endpoint Process
      • [get|post|put|delete]OutputOverride(data): Intended method for data modification / override (Output data), it also set that information to this.response.dome.output, from where can be used for other methods

        • Post Endpoint Process
      • [get|post|put|delete]Process(): Actual process / logic for this endpoint, by default it just return { data : "get" };, this should be overrided with the intended behaviour.

      • [get|post|put|delete](): Do not override, this is the orchestrator of the others / prev methods.

  • templates

    These file are copied each time you decide to add a new endpoint, it has the need extensions to use the support files.

    • accessPoint.js: Route managedment, it extends from support/accessPoint

    • businessLogic.js: Process execution for the specific endpoint, here can be override most of the default method of support/businessLogic.js (but no [get|post|put|delete]()), is also the right place to define other kind of logic related to the endpoint logic