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

microfeedback-core

v3.0.0

Published

The core library for creating microfeedback backends.

Downloads

18

Readme

microfeedback-core

Build Status Greenkeeper badge

Core library for building microfeedback backends.

What is a microfeedback backend?

In short: an easily-deployable HTTP microservice for collecting user feedback about your apps.

Installation

Requires Node>=8.

npm install microfeedback-core --save

Usage

The microfeedback function is the only public API. It takes a backend function which contains the code to handle user feedback (e.g. post a GitHub issue, send an email) sent from a client. The second argument, attributes, is an Object that describes the backend (e.g. name, version, description).

The first argument to the backend function contains the input which will contain--at a minimum--an entry named body with the feedback content.

If the PERSPECTIVE_API_KEY environment variable is set, the first argument will contain a perspective Object with information returned from the Perspective API.

If the AKISMET_API_KEY environment variable is set, input will be checked with the Akismet API. If spam is detected, an error response will be returned. If the ALLOW_SPAM environment variable is set, an error response will not be returned and the first argument to the backend will contain an akismet Object of the form {spam: Boolean}.

Perspective and Akismet support can be disabled by setting PERSPECTIVE_ENABLED=false and AKISMET_ENABLED=false in the environment.

The backend function also receives the request (req) and response (res) objects. See the node http docs for more information about these objects.

The microfeedback function returns a micro request handler.

// index.js
const { createError } = require('micro');
const microfeedback = require('microfeedback');
const sendEmail = require('./email-library');

const EmailBackend = async ({input, perspective, akismet}, req, res) => {
  const {name, body} = input;
  const toxicity = perspective ? perspective.toxicity : null;
  const email = process.env.FEEDBACK_EMAIL;  // where to receive feedback
  const subject = '[microfeedback] Feedback posted' + name ? `by ${name}` : '';
  const content = `${name} posted feedback on your app:

${body}

${toxicity ? `Toxicity rating: ${toxicity}` : ''}

Cheers,
The microfeedback Robot`;
  try {
    const result = await sendEmail(email, {subject, content});
    return { status: result.status };
  } catch (err) {
    throw createError(400, 'Could not send email', err);
  }
};

module.exports = microfeedback(EmailBackend, {
  name: 'email',
  version: '1.0.0',
});

The service can then be run with the micro CLI via npm start.

{
  "name": "microfeedback-email",
  "dependencies": {
    "micro": "x.y.z",
    "microfeedback-core": "x.y.z"
  },
  "main": "index.js",
  "scripts": {
    "start": "micro"
  }
}
npm start

Backends

Development

  • Fork and clone this repo. cd into the project directory.
  • npm install
  • To run tests: npm test
  • To run the example server with auto-reloading: npm run dev

Debugging in tests with iron-node

Add debugger statements, then run the following:

npm install -i iron-node
npm run test:debug

License

MIT Licensed.