# Contributing Suggestions and pull requests are highly encouraged. Have a look at the [open issues](https://github.com/NotionX/react-notion-x/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22+sort%3Areactions-%2B1-desc), especially [the easy ones](https://github.com/NotionX/react-notion-x/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22+sort%3Areactions-%2B1-desc). ## Development To develop the project locally, you'll need a recent version of Node.js and `pnpm` installed globally. To get started, clone the repo and run `pnpm` from the root directory: ```bash git clone https://github.com/transitive-bullshit/nextjs-notion-starter-kit cd nextjs-notion-starter-kit pnpm ``` Now that your dependencies are installed, you can run the local Next.js dev server: ```bash pnpm dev ``` You should now be able to open `http://localhost:3000` to view the webapp. ## Production To build for production, you can run: ```bash pnpm build ``` Which just runs `next build` under the hood. ### Local-linked react-notion-x If you are making changes to `react-notion-x` and want to test them out with `nextjs-notion-starter-kit`, you'll first need to [set up and build `react-notion-x` locally](https://github.com/NotionX/react-notion-x/blob/master/contributing.md). Once you have `react-notion-x` set up and built locally, you can link these local deps into `nextjs-notion-starter-kit`: ```bash pnpm deps:link ``` With this setup, in one tab, you can run `pnpm dev` to keep `react-notion-x` up-to-date, and in another tab, you can run `pnpm dev` to keep `nextjs-notion-starter-kit` up-to-date. ### Gotchas Whenever you make a change to one of the `react-notion-x` packages, it will automatically be recompiled into its respective `build` folder, and the `pnpm dev` from `nextjs-notion-starter-kit` should hot-reload it in the browser. Sometimes, this process gets a little out of whack, and if you're not sure what's going on, I usually just quit one or both of the `pnpm dev` commands and restart them. If you're seeing something unexpected while debugging with Next.js, try running `rm -rf .next` to refresh the Next.js cache before running `pnpm dev` again.