|
| 1 | +# AdonisJS package starter kit |
| 2 | + |
| 3 | +> A boilerplate for creating AdonisJS packages |
| 4 | +
|
| 5 | +This repo provides you with a starting point for creating AdonisJS packages. Of course, you can create a package from scratch with your folder structure and workflow. However, using this starter kit can speed up the process, as you have fewer decisions to make. |
| 6 | + |
| 7 | +## Setup |
| 8 | + |
| 9 | +- Clone the repo on your computer, or use `giget` to download this repo without the Git history. |
| 10 | + ```sh |
| 11 | + npx giget@latest gh:adonisjs/pkg-starter-kit |
| 12 | + ``` |
| 13 | +- Install dependencies. |
| 14 | +- Update the `package.json` file and define the `name`, `description`, `keywords`, and `author` properties. |
| 15 | +- The repo is configured with an MIT license. Feel free to change that if you are not publishing under the MIT license. |
| 16 | + |
| 17 | +## Folder structure |
| 18 | + |
| 19 | +The starter kit mimics the folder structure of the official packages. Feel free to rename files and folders as per your requirements. |
| 20 | + |
| 21 | +``` |
| 22 | +├── providers |
| 23 | +├── src |
| 24 | +├── bin |
| 25 | +├── stubs |
| 26 | +├── configure.ts |
| 27 | +├── index.ts |
| 28 | +├── LICENSE.md |
| 29 | +├── package.json |
| 30 | +├── README.md |
| 31 | +├── tsconfig.json |
| 32 | +├── tsnode.esm.js |
| 33 | +``` |
| 34 | + |
| 35 | +- The `configure.ts` file exports the `configure` hook to configure the package using the `node ace configure` command. |
| 36 | +- The `index.ts` file is the main entry point of the package. |
| 37 | +- The `tsnode.esm.js` file runs TypeScript code using TS-Node + SWC. Please read the code comment in this file to learn more. |
| 38 | +- The `bin` directory contains the entry point file to run Japa tests. |
| 39 | +- Learn more about [the `providers` directory](./providers/README.md). |
| 40 | +- Learn more about [the `src` directory](./src/README.md). |
| 41 | +- Learn more about [the `stubs` directory](./stubs/README.md). |
| 42 | + |
| 43 | +### File system naming convention |
| 44 | + |
| 45 | +We use `snake_case` naming conventions for the file system. The rule is enforced using ESLint. However, turn off the rule and use your preferred naming conventions. |
| 46 | + |
| 47 | +## Peer dependencies |
| 48 | + |
| 49 | +The starter kit has a peer dependency on `@adonisjs/core@6`. Since you are creating a package for AdonisJS, you must make it against a specific version of the framework core. |
| 50 | + |
| 51 | +If your package needs Lucid to be functional, you may install `@adonisjs/lucid` as a development dependency and add it to the list of `peerDependencies`. |
| 52 | + |
| 53 | +As a rule of thumb, packages installed in the user application should be part of the `peerDependencies` of your package and not the main dependency. |
| 54 | + |
| 55 | +For example, if you install `@adonisjs/core` as a main dependency, then essentially, you are importing a separate copy of `@adonisjs/core` and not sharing the one from the user application. Here is a great article explaining [peer dependencies](https://blog.bitsrc.io/understanding-peer-dependencies-in-javascript-dbdb4ab5a7be). |
| 56 | + |
| 57 | +## Published files |
| 58 | + |
| 59 | +Instead of publishing your repo's source code to npm, you must cherry-pick files and folders to publish only the required files. |
| 60 | + |
| 61 | +The cherry-picking uses the `files` property inside the `package.json` file. By default, we publish the following files and folders. |
| 62 | + |
| 63 | +```json |
| 64 | +{ |
| 65 | + "files": ["build/src", "build/providers", "build/stubs", "build/index.d.ts", "build/index.js"] |
| 66 | +} |
| 67 | +``` |
| 68 | + |
| 69 | +If you create additional folders or files, mention them inside the `files` array. |
| 70 | + |
| 71 | +## Exports |
| 72 | + |
| 73 | +[Node.js Subpath exports](https://nodejs.org/api/packages.html#subpath-exports) allows you to define the exports of your package regardless of the folder structure. This starter kit defines the following exports. |
| 74 | + |
| 75 | +```json |
| 76 | +{ |
| 77 | + "exports": { |
| 78 | + ".": "./build/index.js", |
| 79 | + "./types": "./build/src/types.js" |
| 80 | + } |
| 81 | +} |
| 82 | +``` |
| 83 | + |
| 84 | +- The dot `.` export is the main export. |
| 85 | +- The `./types` exports all the types defined inside the `./build/src/types.js` file (the compiled output). |
| 86 | + |
| 87 | +Feel free to change the exports as per your requirements. |
| 88 | + |
| 89 | +## Testing |
| 90 | + |
| 91 | +We configure the [Japa test runner](https://japa.dev/) with this starter kit. Japa is used in AdonisJS applications as well. Just run one of the following commands to execute tests. |
| 92 | + |
| 93 | +- `npm run test`: This command will first lint the code using ESlint and then run tests and report the test coverage using [c8](https://github.com/bcoe/c8). |
| 94 | +- `npm run quick:test`: Runs only the tests without linting or coverage reporting. |
| 95 | + |
| 96 | +The starter kit also has a Github workflow file to run tests using Github Actions. The tests are executed against `Node.js 20.x` and `Node.js 21.x` versions on both Linux and Windows. Feel free to edit the workflow file in the `.github/workflows` directory. |
| 97 | + |
| 98 | +## TypeScript workflow |
| 99 | + |
| 100 | +- The starter kit uses [tsc](https://www.typescriptlang.org/docs/handbook/compiler-options.html) for compiling the TypeScript to JavaScript when publishing the package. |
| 101 | +- [TS-Node](https://typestrong.org/ts-node/) and [SWC](https://swc.rs/) are used to run tests without compiling the source code. |
| 102 | +- The `tsconfig.json` file is extended from [`@adonisjs/tsconfig`](https://github.com/adonisjs/tooling-config/tree/main/packages/typescript-config) and uses the `NodeNext` module system. Meaning the packages are written using ES modules. |
| 103 | +- You can perform type checking without compiling the source code using the `npm run type check` script. |
| 104 | + |
| 105 | +Feel free to explore the `tsconfig.json` file for all the configured options. |
| 106 | + |
| 107 | +## ESLint and Prettier setup |
| 108 | + |
| 109 | +The starter kit configures ESLint and Prettier. Both configurations are stored within the `package.json` file and use our [shared config](https://github.com/adonisjs/tooling-config/tree/main/packages). Feel free to change the configuration, use custom plugins, or remove both tools altogether. |
| 110 | + |
| 111 | +## Using Stale bot |
| 112 | + |
| 113 | +The [Stale bot](https://github.com/apps/stale) is a Github application that automatically marks issues and PRs as stale and closes after a specific duration of inactivity. |
| 114 | + |
| 115 | +Feel free to delete the `.github/stale.yml` and `.github/lock.yml` files if you decide not to use the Stale bot. |
0 commit comments