chimp

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

Usage
Commands

Usage

$ npm install -g chimp
$ chimp COMMAND
running command...
$ chimp (--version)
chimp/0.0.0-development darwin-arm64 node-v18.1.0
$ chimp --help [COMMAND]
USAGE
  $ chimp COMMAND
...

Commands

chimp create NAME
chimp eject
chimp generate
chimp help [COMMANDS]
chimp init

`chimp create NAME`

create (scaffold) a new app

USAGE
  $ chimp create NAME [-h] [-a <value>] [-g <value>]

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

FLAGS
  -a, --appPrefix=<value>        [default: ~app] prefix that points to the sourcecode of your app
  -g, --generatedPrefix=<value>  [default: ~generated] prefix that points to the generated by chimp helper code
  -h, --help                     Show CLI help.

DESCRIPTION
  create (scaffold) a new app

EXAMPLES
  $ chimp create my-new-app

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

See code: src/commands/create.ts

`chimp eject`

Eject from chimp. While chimp is not a runtime dependency and your project will still run after removing it, ejecting offers a cleaner development environment. While we hope you never need to eject, it is reassuring to know you have the option. If you choose to eject or are considering it, please inform us. Remember, you are always just one command away from this choice.

USAGE
  $ chimp eject [-h]

FLAGS
  -h, --help  Show CLI help.

DESCRIPTION
  Eject from chimp. While chimp is not a runtime dependency and your project will still run after removing it, ejecting
  offers a cleaner development environment. While we hope you never need to eject, it is reassuring to know you have the
  option. If you choose to eject or are considering it, please inform us. Remember, you are always just one command away
  from this choice.

EXAMPLES
  $ chimp eject

See code: src/commands/eject.ts

`chimp generate`

generate GraphQL code

USAGE
  $ chimp generate [-h] [-a <value>] [-g <value>] [-p <value>]

FLAGS
  -a, --appPrefix=<value>        [default: ~app] prefix that points to the sourcecode of your app
  -g, --generatedPrefix=<value>  [default: ~generated] prefix that points to the generated by chimp helper code
  -h, --help                     Show CLI help.
  -p, --modulesPath=<value>      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

DESCRIPTION
  generate GraphQL code

EXAMPLES
  $ chimp generate

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

See code: src/commands/generate.ts

`chimp help [COMMANDS]`

Display help for chimp.

USAGE
  $ chimp help [COMMANDS] [-n]

ARGUMENTS
  COMMANDS  Command to show help for.

FLAGS
  -n, --nested-commands  Include all nested commands in the output.

DESCRIPTION
  Display help for chimp.

See code: @oclif/plugin-help

`chimp init`

init Chimp

USAGE
  $ chimp init [-h] [-p <value>]

FLAGS
  -h, --help                 Show CLI help.
  -p, --modulesPath=<value>  [default: ./src/modules] path to the GraphQL modules.

DESCRIPTION
  init Chimp

EXAMPLES
  $ chimp init

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

See code: src/commands/init.ts

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>/"
  })
}