contributing.md

Contributing Guide

Thanks for your interest in contributing to serve! This guide will show you how to set up your environment and contribute to this library.

Set Up

First, you need to install and be familiar the following:

• git: Here is a great guide by GitHub on installing and getting started with Git.
• node and pnpm: This guide will help you install Node and this one will help you install PNPM. The recommended method is using the n version manager if you are on MacOS or Linux. Make sure you are using the current version of Node.

Once you have installed the above, follow these instructions to fork and clone the repository (vercel/serve).

Once you have forked and cloned the repository, you can pick out an issue you want to fix/implement!

Making Changes

Once you have cloned the repository to your computer (say, in ~/code/serve) and picked the issue you want to tackle, create a branch:

> git switch --create branch-name

While naming your branch, try to follow the below guidelines:

1. Prefix the branch name with the type of change being made:
   • fix: For a bug fix.
   • feat: For a new feature.
   • test: For any change related to tests.
   • perf: For a performance related change.
   • build: For changes related to the build process.
   • ci: For all changes to the CI files.
   • refc: For any refactoring work.
   • docs: For any documentation related changes.
2. Make the branch name short but self-explanatory.

Once you have created a branch, you can start coding!

The CLI is written in Typescript and uses the current version of Node. The code is structured as follows:

serve
├── config
│  └── husky
│     ├── _
│     └── pre-commit
├── media
│  ├── banner.png
│  └── listing-ui.png
├── source
│  ├── utilities
│  │  ├── cli.ts
│  │  ├── config.ts
│  │  ├── http.ts
│  │  ├── logger.ts
│  │  ├── promise.ts
│  │  └── server.ts
│  ├── main.ts
│  └── types.ts
├── contributing.md
├── license.md
├── package.json
├── pnpm-lock.yaml
├── readme.md
└── tsconfig.json

Most files have a little description of what they do at the top.

./

• package.json: Node package manifest. This file contains the name, version, description, dependencies, scripts and package configuration of the project.
• pnpm-lock.yaml: PNPM lock file, please do not modify it manually. Run pnpm install to update it if you add/remove a dependency to/from package.json manually.
• tsconfig.json: The Typescript configuration for this project.
• contributing.md: The file you are reading. It helps contributors get started.
• license.md: Tells people how they can use the code.
• readme.md: The file everyone should read before running the server. Contains installation and usage instructions.

config/husky/

• pre-commit: This file is a script that runs before Git commits code.

source/utilities/

• utilities/config.ts: Searches and parses the configuration for the CLI.
• utilities/http.ts: Defines and exports helper functions for the server.
• utilities/server.ts: Exports a function used to start the server with a given configuration on a certain port.
• utilities/promise.ts: Exports utility functions and wrappers that help resolve Promises.
• utilities/cli.ts: Exports functions that help with CLI-related stuff, e.g., parsing arguments and printing help text.
• utilities/logger.ts: A barebones logger.

source/

• main.ts: Entrypoint for the CLI.
• types.ts: Typescript types used in the project.

When adding a new feature/fixing a bug, please add/update the readme. Also make sure your code has been linted and that existing tests pass. You can run the linter using pnpm lint, the tests using pnpm test and try to automatically fix most lint issues using pnpm lint --fix.

You can run the CLI tool using pnpm develop, which will re-run the CLI everytime you save changes made to the code.

Once you have made changes to the code, you will want to commit (basically, Git's version of save) the changes. To commit the changes you have made locally:

> git add this/folder that/file
> git commit --message 'commit-message'

While writing the commit-message, try to follow the below guidelines:

1. Prefix the message with type:, where type is one of the following dependending on what the commit does:
   • fix: Introduces a bug fix.
   • feat: Adds a new feature.
   • test: Any change related to tests.
   • perf: Any performance related change.
   • build: For changes related to the build process.
   • ci: For all changes to the CI files.
   • refc: Any refactoring work.
   • docs: Any documentation related changes.
2. Keep the first line brief, and less than 60 characters.
3. Try describing the change in detail in a new paragraph (double newline after the first line).

Contributing Changes

Once you have committed your changes, you will want to push (basically, publish your changes to GitHub) your commits. To push your changes to your fork:

> git push -u origin branch-name

If there are changes made to the main branch of the vercel/serve repository, you may wish to rebase your branch to include those changes. To rebase, or include the changes from the main branch of the vercel/serve repository:

> git fetch upstream main
> git rebase upstream/main

This will automatically add the changes from main branch of the vercel/serve repository to the current branch. If you encounter any merge conflicts, follow this guide to resolve them.

Once you have pushed your changes to your fork, follow these instructions to open a pull request:

Once you have submitted a pull request, the maintainers of the repository will review your pull requests. Whenever a maintainer reviews a pull request they may request changes. These may be small, such as fixing a typo, or may involve substantive changes. Such requests are intended to be helpful, but at times may come across as abrupt or unhelpful, especially if they do not include concrete suggestions on how to change them. Try not to be discouraged. If you feel that a review is unfair, say so or seek the input of another project contributor. Often such comments are the result of a reviewer having taken insufficient time to review and are not ill-intended. Such difficulties can often be resolved with a bit of patience. That said, reviewers should be expected to provide helpful feedback.

In order to land, a pull request needs to be reviewed and approved by at least one maintainer and pass CI. After that, if there are no objections from other contributors, the pull request can be merged.

Congratulations and thanks for your contribution!