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

@jmvtrinidad/chimp

v5.0.0

Published

Your development companion for doing quality, faster.

Downloads

2

Readme

chimp

Your development companion for doing quality, faster. For a full documentation please go to chimpjs.com.

oclif Version Downloads/week License

Usage

$ npm install -g @jmvtrinidad/chimp
$ chimp COMMAND
running command...
$ chimp (-v|--version|version)
@jmvtrinidad/chimp/5.0.0 linux-x64 node-v14.20.1
$ chimp --help [COMMAND]
USAGE
  $ chimp COMMAND
...

Commands

chimp create [NAME]

create (scaffold) a new app

USAGE
  $ chimp create [NAME]

ARGUMENTS
  NAME  name of the new app, also used as the directory

OPTIONS
  -a, --appPrefix=appPrefix              [default: ~app] prefix that points to the sourcecode of your app
  -g, --generatedPrefix=generatedPrefix  [default: ~generated] prefix that points to the generated by chimp helper code
  -h, --help                             show CLI help

EXAMPLES
  $ chimp create my-new-app
  $ chimp create my-new-app -a ~src -g ~chimp-helpers

chimp generate

generate GraphQL code

USAGE
  $ chimp generate

OPTIONS
  -a, --appPrefix=appPrefix              [default: ~app] prefix that points to the sourcecode of your app
  -g, --generatedPrefix=generatedPrefix  [default: ~generated] prefix that points to the generated by chimp helper code
  -h, --help                             show CLI help

  -p, --modulesPath=modulesPath          path to the graphQL modules, only use if you are migrating an existing Apollo
                                         App and you want to use chimp only for a part of it

EXAMPLES
  $ chimp generate
  $ chimp generate -a ~src -g ~chimp-helpers

chimp help [COMMAND]

display help for chimp

USAGE
  $ chimp help [COMMAND]

ARGUMENTS
  COMMAND  command to show help for

OPTIONS
  --all  see all commands in CLI

See code: @oclif/plugin-help

chimp init

init Chimp

USAGE
  $ chimp init

OPTIONS
  -h, --help                     show CLI help
  -p, --modulesPath=modulesPath  [default: ./src/modules] path to the GraphQL modules.

EXAMPLES
  $ chimp init
  $ chimp init -p ./src/chimp-modules

Updating jest.config.js after chimp init

Please manually add pathsToModuleNameMapper like so:

const { pathsToModuleNameMapper } = require("ts-jest/utils");
const { compilerOptions } = require("./tsconfig");
// ...
module.exports = {
  // ...,
  moduleNameMapper: pathsToModuleNameMapper(compilerOptions.paths, {
    prefix: "<rootDir>/"
  })
}