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

@artifacter/webapi

v1.0.1

Published

Artifacter's Web API

Downloads

9

Readme

artifacter-logo@artifacter/webapi

Artifacter's artifacts webapi core connector

Checkout Github's parsed README for a better visualization! -> https://github.com/arthmoeros/artifacter-webapi

What's this? - Intro

This is Artifacter's Web API connector for the core (previously coupled with @artifacter/core), it makes use of the core module to expose all its API via a RESTful API.

How do I use this?

You can git clone this same repo and start it just like this

git clone https://github.com/arthmoeros/artifacter-webapi/
npm install
npm start

...or use it as a npm package, and start it using the provided bin

npm install --save @artifacter/webapi
node_modules/.bin/artifacter-serve

In both cases, by default the config and temporary directories are within the core base folder, you can customize these paths using the environment variables ARTIFACTER_CONFIG and ARTIFACTER_TMP, here is a unix example:

# Default is ./config
export ARTIFACTER_CONFIG=/etc/artifacter_custom
# Default is ./tmp
export ARTIFACTER_TMP=/var/artifacter_custom

What's in here? - API

Artifacter's Web API runs as an expressJS server, it has the same 4 services available in the API as the core, via RESTful.


Get Form Configurations list

Resource | Method | Request ContentType | Response ContentType -------- | ------ | --------------------- | ----------------------- /forms | GET | application/x-www-form-urlencoded | application/json

Retrieves a list of presumably valid form configurations ids on the configuration path of Artifacter. It returns a string array containing each form configuration ID (file name without extension).

Get Form Configuration

Resource | Method | Request ContentType | Response ContentType -------- | ------ | --------------------- | ----------------------- /forms/:id | GET | application/x-www-form-urlencoded | application/json

Retrieves the contents of a identified form configuration file on Artifacter as a json string.

Request Artifact Generation

Resource | Method | Request ContentType | Response ContentType -------- | ------ | --------------------- | ----------------------- /generatedArtifacts | POST | application/json | application/json

Requests an artifact generation and returns an uuid to retrieve the generated artifacts. The RESTful API responds with the location of the created resource (generated artifact) in the Location header.

Retrieve generated artifacts

Resource | Method | Request ContentType | Response ContentType -------- | ------ | --------------------- | ----------------------- /generatedArtifacts/:uuid | GET | application/x-www-form-urlencoded | application/zip

Retrieves a generated artifact, once is retrieved it is deleted from the temporary folder, any subsequent try to get the same artifact will result in a 404 status code.


How do I handle all the Configuration? - Artifacter's Core Configuration

Check out the @artifacter/core README