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

feedback-to-gitlab

v1.1.4

Published

Express middleware to generate Gitlab issues from visual user feedback

Downloads

29

Readme

feedback-to-gitlab

Express middleware to create Gitlab issues from user feedback generated by ivoviz/feedback

Screenshot

Installation

npm install feedback-to-gitlab

Usage

var express = require('express')
var feedback = require('feedback-to-gitlab')
var app = express()

app.post('/feedback', feedback({
  url: 'https://gitlab.url.com',
  token: 'abcdefghij123456',
  repository: 'some/repo'
}))

app.listen(80)

On the website where you want to gain user feedback you have to include ivoviz/feedback. Example configuration:

jQuery.feedback({
  ajaxURL: 'http://url.com/feedback',
  html2canvasURL: 'html2canvas.min.js'
})

A method do run feedback-to-gitlab in a docker container is described in the wiki.

Configuration

url (String, required)

Base url of your Gitlab instance.

token (String, required)

User token for Gitlab.

repository (String or Number, required)

The path with namespace (e.g. 'some/repo') or ID (123) of the Gitlab repository where the issues are created.

auth (Object)

User credentials of the form { user: 'some', password: 'credentials' } if your Gitlab instance requires HTTP basic access authentication.

Default: null

labels (Array)

List of labels to tag the created issue.

Default: [ 'new' ]

store.repository (String or Number)

By default the screenshots are uploaded to the same repository where the issue is created. Use this option to define a different repository by its namespace (e.g. 'some/other-repo') or ID (124).

Default: repository

store.branch (String)

Name of the branch where the screenshots will be stored.

Default: 'master'

store.path (String)

Directory where the screenshots will be stored in the repository.

Default: 'screenshots'

store.limit (String)

Limit the file size of the screenshot.

Default: '1mb'