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

@digigov-oss/find-passport-by-parameters-client

v1.0.2

Published

Client for findPassportByParametersClient service of GSIS

Downloads

41

Readme

Client for findPassportByParameters service of KED

Client to connect to findPassportByParameters service, useful for nextjs/nodejs projects.

Example:

import findPassportByPassportNumber from '@digigov-oss/find-passport-by-parameters-client';

const test = async () => {
   const overrides = {
        prod:false,
        auditInit: {
            auditUnit: 'grnet.gr',
        },
        auditStoragePath: '/auditStorage',
    }

    try {
        return await findPassportByPassportNumber("AB1234567", "username", "password", overrides);
    } catch (error) {
        console.log(error);
    }
}

test().then((r) => { console.log('findPassportByPassportNumber', r); });
  • you can use overrides to override the default values
  • for your tests, you don't need to use the overrides mecahnism,in that case, the default storage path will be used ie /tmp
  • look at KED standard guides for records you can use on auditInit" Also, you can use overrides to override the default storage engine.
import findPassportByPassportNumber from '@digigov-oss/find-passport-by-parameters-client';
import {PostgreSqlEngine} from '@digigov-oss/gsis-audit-record-db'; 

const test = async () => {
    try {
        const overrides = {
        auditEngine: new PostgreSqlEngine('postgres://postgres:postgres@localhost:5432/postgres'),
        auditInit: {
            auditUnit: 'grnet.gr',
        },
        }
        return await findPassportByPassportNumber("AB1234567", "username", "password", overrides);
    } catch (error) {
        console.log(error);
    }
}

test().then((r) => { console.log('findPassportByPassportNumber', r); });

Look at module AuditRecordDB for more details on how to use the AuditEngine.

If you plan to use only the FileEngine, you can skip the installation of other engines by ignoring optional dependencies. i.e. yarn install --ignore-optional

Returns

an object like the following:

TODO

or an error message like:

TODO

Available data for testing:

000152418

* Notes

you have to ask KED for policePassportService_v1.3 documentation to get more info about the output and error fields.

* known issues

If KED advertises a wrong endpoint for the service on production WSDL, you can override the endpoint on the overrides object.

const overrides = {
    endpoint: 'my new endpoint here',
}