|
8 | 8 |
|
9 | 9 | ## Features
|
10 | 10 |
|
11 |
| -This template offers following pre-configured features. Additionally, your repo will automatically be rebranded with help of workflow and post install scripts. |
12 |
| - |
13 |
| -✅ Monorepo powered by turbo repo to build, test and deploy your library |
14 |
| - |
15 |
| -✅ Next.js, Vite and Remix examples to demonstrate how your library can be used (Feel free to remove Remix as it is still unstable when it comes to monorepo setup and importing from folders) |
16 |
| - |
17 |
| -✅ Examples pre-configured to use Light/Dark theme according to user preference |
18 |
| - |
19 |
| -✅ The examples provided are ready to be deployed to Vercel |
20 |
| - |
21 |
| -✅ Typedoc setup to automatically create documentation for your library based on tsdoc comments |
22 |
| - |
23 |
| -✅ Code of Conduct and contributing files that you can always update |
24 |
| - |
25 |
| -✅ Prettier and linter configured as per the modern best practices (Feel free to add your flavour) |
26 |
| - |
27 |
| -✅ Recommended VSCode extensions - Prettier and [Kanban board](https://github.com/mayank1513/vscode-extension-trello-kanban-board) to auto-format your code and manage your project priorities right within your IDE |
28 |
| - |
29 |
| -✅ Powerful code generators - try yarn turbo gen |
30 |
| - |
31 |
| -✅ Test setup with Vitest - A modern and fast testing framework supporting Jest like APIs |
32 |
| - |
33 |
| -✅ Workflows to automate running tests on every pull-request or code push events |
34 |
| - |
35 |
| -✅ Workflow to automatically publish and create a GitHub release when you update your librari's `package.json` file. |
36 |
| - |
37 |
| -✅ Workflow to automatically rebrand entire template based on the name of the repo you create from this template. (As soon as you create a repo from this template, setup workflow is triggered which renames fork-me to your repo name and does lots of other fixes to set you up and running.) |
38 |
| - |
39 |
| -✅ With all these features, this readme file contains a quick checklist for you to configure Codecov and other badges, setup your docs website on GitHub pages, etc. See [Checklist](#step-by-step-instructions-and-checklist). |
40 |
| - |
41 |
| -#### Create a library that is |
42 |
| - |
43 | 11 | ✅ Fully Treeshakable (import from fork-me/client/component)
|
44 | 12 |
|
45 | 13 | ✅ Full TypeScript Support
|
@@ -89,20 +57,6 @@ Compared to the default scaffold from create-turbo, this template offers:
|
89 | 57 |
|
90 | 58 | ## Step by Step Instructions and Checklist
|
91 | 59 |
|
92 |
| -- [ ] Star [this repo](https://github.com/react18-tools/fork-me/) so that you and others can find it more easily for your next projects. It also helps me understand that people are using this repo so that I can maintain the repo and the documentation well. |
93 |
| - |
94 |
| - |
95 |
| - |
96 |
| - |
97 |
| -- [ ] Install and setup Node.js and IDE (I prefer VSCode) |
98 |
| -- [ ] Install the recommended VSCode extensions - [Prettier](https://marketplace.visualstudio.com/items?itemName=esbenp.prettier-vscode), [Trello Kanban](https://marketplace.visualstudio.com/items?itemName=mayank1513.trello-kanban-task-board) |
99 |
| -- [ ] Install dependencies using `pnpm` |
100 |
| - - [ ] If you don't have `pnpm` installed, run `npm i -g pnpm` to install `pnpm` -> run `pnpm setup` to set up `pnpm` for global installations |
101 |
| - - [ ] Run `pnpm i` to install dependencies and `preinstall` script will automatically touch up workflows and create a commit |
102 |
| - - [ ] Run `pnpm i -g turbo` to install `turbo` globally (Sometime due to `TypeScript` and `Plop` version conflicts code generation requires global `turbo`). |
103 |
| - - [ ] Run `turbo gen react-component`, and follow prompts to generate server or client components for your library |
104 |
| - - [ ] Use `snake-case` for your component name - it will be automatically converted to `PascalCase` |
105 |
| - - [ ] Your component and test files will be created in `**/src/client/` or `**/src/server/` directory depending on whether you choose `client` or `server` component |
106 | 60 | - [ ] run `node scope.js` from the root directory if you want to publish scoped pacckage.
|
107 | 61 | - [ ] We assumed that your npm user name is same as your GitHub account or organization username.
|
108 | 62 | - [ ] Please make sure `owner` is set to your <npmjs.com> username before running the above command.
|
|
0 commit comments