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

@mvf/servicer-sqs

v1.3.2

Published

## Usage

Downloads

131

Readme

MVF Servicer SQS

Usage

TODO

To install the package

Run npm install @mvf/servicer-sqs

Configuration

Set the following environment variables in your project

  • ENVIRONMENT_FILE should be set to development | testing | staging | production

Servicer SQS

First setup sqs service, create src/Services/Sqs.ts

import { SQS } from '@aws-sdk/client-sqs';
import Environment from '../Setup/Environment';

let client: SQS | undefined;

export const Sqs = (): SQS => {
  if (!client) {
    const endpoint = Environment.AWS_ENDPOINT;
    client = endpoint
      ? new SQS({
          endpoint,
          credentials: {
            accessKeyId: 'dev',
            secretAccessKey: 'dev',
          },
        })
      : new SQS({});
  }

  return client;
};

Then setup SqsDaemon, create src/Setup/Sqs/SqsDaemon.ts

import { SqsMany, sqsConfig } from '@mvf/servicer-sqs';
import Environment from '../Environment';
import {
  InternalSqsEvents,
} from '../../EventSources/Sqs';
import { Sqs } from '../../Services/Sqs';

const template = Environment.SQS_URL_TEMPLATE;

export const SqsDaemon = new SqsMany([
  sqsConfig(InternalSqsEvents, template, 'internal', Sqs()),
  // Add sqs config for each sqs queue you want to consume from 
]);

Finally setup app entrypoint, create src/entrypoint.ts

import { Application, DaemonCommand } from "@mvf/servicer";
import { SqsDaemon } from './Setup/Sqs/SqsDaemon';

const setupApplication = async (): Promise<void> => {
  const application = new Application();

  application.addCommands(
    new DaemonCommand(SqsDaemon),
  );

  await application.run();
};

void setupApplication();

Contributing

Setup

  • Run make to build the container
  • Run make shell to enter the container
  • Run npm install to install dependencies

Refer to package.json for commands

After merging

After you have merged a PR to master, you need to rebuild and publish your changes.

  1. Checkout master git checkout master && git pull
  2. Use one of the following make publish commands to publish changes:
    • make publish kind=patch - Use this if your change is a bug fix and is backwards compatible.
    • make publish kind=minor - Use this if your change adds new functionality and is backwards compatible.
    • make publish kind=major - Use this if your change is not backwards compatible.