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

@emarketeer/ts-microservice-commons

v6.3.1

Published

A common config for eMarketeer TypeScript microservice

Downloads

586

Readme

eMarketeer TypeScript Microservice Commons

A common config for eMarketeer TypeScript microservice

Contents

  • Common ts.config.json
  • Common webpack config
  • Common parts of serverless.yml including Epsagon configuration
  • Common eslint config
  • Common jest config

How to use

  1. Clone em-ts-microservice-starter
  2. Rename all occurences of em-ts-microservice-starter to whatever your service is going to be named

Scripts

Following commands are available:

  • em-commons lint
  • em-commons tsc
  • em-commons jest
  • em-commons deploy
  • em-commons invoke-local

jest

Please note that test will run in parallel. If you need to do a global setup/teardown before/after running your tests, the default configuration is like this:

  "globalSetup": "<rootDir>/src/utils/func-test-setup.ts",
  "globalTeardown": "<rootDir>/src/utils/func-test-teardown.ts",

Example func-test-setup.ts file:

import { addCurrentHostToSecurityGroup, initTestRuntime } from './test.utils'

const setup = async () => {
  await initTestRuntime()
  await addCurrentHostToSecurityGroup('...', ...)
}

export default setup

Example func-test-teardown.ts file:

import { removeCurrentHostFromSecurityGroup } from './test.utils'

const teardown = async () => {
  await removeCurrentHostFromSecurityGroup('...', ...)
}

export default teardown

invoke-local

This command runs a lambda locally.

Example usage:

yarn invoke-local -f example-handler -d "hello world"

Where -f is the function name and -d is the request data.

More information on arguments is available here: https://www.serverless.com/framework/docs/providers/aws/cli-reference/invoke-local/

test local

In this directory:

yarn build

yarn link

In project directory: yarn link @emarketeer/ts-microservice-commons

To unlink: yarn unlink @emarketeer/ts-microservice-commons

release

Create a commit following the syntax of https://github.com/semantic-release/semantic-release#commit-message-format