You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -84,25 +84,25 @@ Make sure you are set up locally by following the [Getting Started](#getting-sta
84
84
- `test:raw`- Runs the binary directly. Rarely used, but can be useful for manual tests where you want to be able to specify the `app_name` argument yourself.
85
85
- `clean`- Removes all generated files, including build files and the `create-next-stack-tests` directory created by the e2e tests.
86
86
87
-
3. Add a new .ts file for your plugin in the plugins directory at `packages\create-next-stack\src\main\plugins`
87
+
3. Add a new .ts file for your plugin in the plugins directory at [`packages/create-next-stack/src/main/plugins`](packages/create-next-stack/src/main/plugins)
88
88
89
89
- See the [Writing a plugin section](#writing-a-plugin) below to learn how to write a Create Next Stack plugin.
90
90
91
-
4. Add new flags to the `create-next-stack` command in [`create-next-stack.ts`](packages\create-next-stack\src\main\commands\create-next-stack.ts).
91
+
4. Add new flags to the `create-next-stack` command in [`create-next-stack.ts`](packages/create-next-stack/src/main/commands/create-next-stack.ts).
92
92
5. Add the plugin to the `plugins` array in [`setup.ts`](packages/create-next-stack/src/main/setup/setup.ts).
93
-
6. Add potential plugin steps to the `steps` array in [`setup.ts`](packages/create-next-stack/src/main/setup/setup.ts). Steps are run top-to-bottom.
94
-
7. Update the [`README.md`](README.md):
95
-
- Add the technology to the technology list
96
-
- Update the `Usage` section by copy pasting the output of running `yarn print:help`
97
-
8. Consider expanding some of the e2e tests to include the new technology. See [`test.ts`](packages\create-next-stack\src\tests\e2e\test.ts) for current tests.
93
+
6. Add potential plugin steps to the `steps` array in [`steps.ts`](packages/create-next-stack/src/main/steps.ts). Steps are run top-to-bottom.
94
+
7. Consider expanding some of the e2e tests to include the new technology. See [`test.ts`](packages/create-next-stack/src/tests/e2e/test.ts) for current tests.
95
+
8. Go and add the technology to the technology selection form of the website.
96
+
- See the [TechnologiesForm](website/templates/LandingPage/components/TechnologiesForm.tsx) component.
97
+
- This component is currently pretty hideous, and updating it will be automated in the future. See [issue #188](https://github.com/akd-io/create-next-stack/issues/188).
98
98
9. Run tests using `yarn test` to ensure they all pass.
99
99
10. Submit a Pull Request on GitHub.
100
100
101
101
## Writing a Plugin
102
102
103
103
Plugins aren't too scary. A Create Next Stack plugin consists of a simple TypeScript file that calls a `createPlugin()` function with JSON object.
104
104
105
-
See the [Framer Motion plugin](packages/create-next-stack/src/main/plugins/emotion.ts) for example. This plugin adds the `framer-motion` npm dependency to the generated Next.js project, as well as adding some documentation about the technology.
105
+
See the [Framer Motion plugin](packages/create-next-stack/src/main/plugins/framer-motion.ts) for example. This plugin adds the `framer-motion` npm dependency to the generated Next.js project, as well as adding some documentation about the technology.
Below you see an overview of Create Next Stack's usage, including detailed information about arguments and options. The overview is the result of running `create-next-stack --help`
62
69
70
+
<!-- CNS-START-OF-HELP-OUTPUT -->
71
+
63
72
```
64
73
USAGE
65
74
$ create-next-stack [APP_NAME] [FLAGS]
66
75
67
76
ARGUMENTS
68
-
APP_NAME The name of your app, optionally including a path prefix. Eg.: "my-app" or "path/to/my-app"
77
+
APP_NAME The name of your app, optionally including a path prefix. Eg.:
78
+
"my-app" or "path/to/my-app"
69
79
70
80
FLAGS
71
81
-h, --help Shows the CLI help information.
72
82
-v, --version Shows the CLI version information.
73
-
--chakra Adds Chakra UI. (Component library) (Requires Emotion and Framer Motion)
74
-
--debug Show verbose error messages for debugging purposes.
75
-
--formatting-pre-commit-hook Adds a formatting pre-commit hook. (Requires Prettier)
83
+
--chakra Adds Chakra UI. (Component library) (Requires
84
+
Emotion and Framer Motion)
85
+
--debug Show verbose error messages for debugging
86
+
purposes.
87
+
--formatting-pre-commit-hook Adds a formatting pre-commit hook. (Requires
0 commit comments