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

@lockerpm/client-service

v1.2.4

Published

## Installation

Downloads

24

Readme

Locker Desktop Service Supporter for Web and Extension

Installation

Install from npm:

npm install -S @lockerpm/client-service

Install from yarn:

yarn add @lockerpm/client-service

Usages

import { WebService, StorageService } from '@lockerpm/client-service'

// Mock secure storage using browser's sessionStorage, you can keep it in others secure storages
// or simply keep it in memory
class WebStorageService implements StorageService {
  secureStorage: {
    [key: string]: any
  }

  constructor() {
    this.secureStorage = {}
  }

  get(key: string) {
    try {
      return Promise.resolve(JSON.parse(sessionStorage.getItem(key) || '') || null)
    } catch (error) {
      return Promise.resolve(null)
    }
  }
  set(key: string, data: any) {
    sessionStorage.setItem(key, JSON.stringify(data))
    return Promise.resolve()
  }
  delete(key: string) {
    sessionStorage.removeItem(key)
    return Promise.resolve()
  }

  getSecure(key: string) {
    // Web client should only keep in memory
    // return Promise.resolve(this.secureStorage[key] || null);
    try {
      return Promise.resolve(JSON.parse(sessionStorage.getItem(`secure___${key}`) || '') || null)
    } catch (error) {
      return Promise.resolve(null)
    }
  }
  setSecure(key: string, data: any) {
    // Web client should only keep in memory
    // this.secureStorage[key] = data;
    sessionStorage.setItem(`secure___${key}`, JSON.stringify(data))
    return Promise.resolve()
  }
  deleteSecure(key: string) {
    // Web client should only keep in memory
    // this.secureStorage[key] = undefined;
    sessionStorage.removeItem(`secure___${key}`)
    return Promise.resolve()
  }
}

const webStorageService = new WebStorageService()

const service = new WebService({
  storageService: webStorageService,
  logLevel: 2,          // 1 for error, 2 for debug
  baseApiUrl: 'https://api.cystack.org/v3',
  clientType: 'web',    // or 'extension'
  domain: 'localhost',  // current domain, used for passkey setup
  serviceAlias: '' // optional, alias of background service
})

// Setup listners
service.on('<event-name>', callback)

Development

Install required packages.

npm install

Run tests

Create a .env file with required access keys (refer to .env.example)

To run all tests, use:

npm test

Testing environment is Node.js, not browser, so window is not working -> some services start with this

// src/services/core-crypto.service.ts

// TEST CONFIG
// import c from 'crypto'
// const crypto = c.webcrypto

// PROD CONFIG
const crypto = window.crypto

You have to uncomment all code bellow // TEST CONFIG and comment all code bellow // PROD CONFIG. Do the oposite when build. You will see error logs of incorrect config.

Run some tests only, please update mocharc.js:

ignore: [
  // './tests/index.spec.ts', // Comment the file you want to test
  './tests/crypto.spec.ts',
  '...'
]