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

@quiches/front

v1.0.0

Published

[![npm](https://img.shields.io/npm/v/@quiches/front?style=for-the-badge)](https://www.npmjs.com/package/@quiches/front) ![GitHub Workflow Status](https://img.shields.io/github/workflow/status/quiches-group/front-js-package/deploy?style=for-the-badge)

Downloads

11

Readme

Filer Server Module

npm GitHub Workflow Status

Description

This package is used to connect and upload files to my file server. To be able to use this service, it is necessary to make me a request for a token. It is also possible to install the file server on your machine but the package is not yet public.

Documentation

1- Installation

Using npm:

$ npm install @quiches/front --save

Using yarn:

$ yarn add @quiches/front

2- Examples

Usage

The public key is generate on dashboard at : https://dashboard.quiches.ovh.

import QuichesStack from '@quiches/front';

const PUBLIC_KEY = 'pub_xxxxx';
const quiches = QuichesStack(PUBLIC_KEY);
const auth = quiches.auth;

// or
import { Authentication } from '@quiches/front';

const PUBLIC_KEY = 'pub_xxxxx';
const auth = new Authentication(PUBLIC_KEY);

3- Authentication

The Authentication class has 3 available methods.

1- Login

This method has 2 parameters which are mail and password, they are of type string.

It returns a promise.

const auth = quiches.auth;

const mail = '[email protected]';
const password = 'passxx';

auth.login({ mail: mail, password: password })
  .then(() => console.log('success'))
  .catch(() => console.log('error'))

2- Register

This method has 4 parameters which are mail, password, firstname and lastanme, they are of type string.

It returns a promise.

const auth = quiches.auth;

const mail = '[email protected]';
const password = 'passxx';
const firstname = 'John';
const lastname = 'Doe';

auth.register({ mail: mail, password: password, firstname: firstname, lastname: lastname })
  .then(() => console.log('success'))
  .catch(() => console.log('error'))

3- Get JWT Token

If you need to retrieve the JWT token to make requests to your API, there is a method to retrieve this token.

If you need to retrieve the JWT token to make requests to your API, there is a method to retrieve this token.

const auth = quiches.auth;

auth.getToken({ mail: mail, password: password })
  .then((token) => console.log(token))
  .catch(() => console.log('error'))