Skip to content
The default Gatsby starter with Typescript and Jest
CSS TypeScript JavaScript
Branch: master
Clone or download
denningk Feature/update readme (#1)
* Update README. Add prerequisites, testing, project structure

* Remove URLs in .gitlab-ci.yml. Add deployment section to readme

* Fix links

* Update .gitlab-ci.yml description in readme to indicate that it's optional
Latest commit 7fd6954 Jun 23, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Start template (#1) May 24, 2019
__mocks__ Feature/add testing (#6) Jun 21, 2019
src Replace anye mention of eatdinkrva with starter. Jun 22, 2019
.editorconfig Replace anye mention of eatdinkrva with starter. Jun 22, 2019
.eslintrc.js Feature/add testing (#6) Jun 21, 2019
.gitignore Feature/add testing (#6) Jun 21, 2019
.gitlab-ci.yml Feature/update readme (#1) Jun 23, 2019
.prettierrc Feature/add testing (#6) Jun 21, 2019
LICENSE Initial commit from gatsby: (… May 24, 2019 Feature/update readme (#1) Jun 23, 2019
gatsby-browser.js Initial commit from gatsby: (… May 24, 2019
gatsby-config.js Replace anye mention of eatdinkrva with starter. Jun 22, 2019
gatsby-node.js Initial commit from gatsby: (… May 24, 2019
jest-preprocess.js Feature/add testing (#6) Jun 21, 2019
jest.config.js Feature/add testing (#6) Jun 21, 2019
loadershim.js Feature/add testing (#6) Jun 21, 2019
package-lock.json Replace anye mention of eatdinkrva with starter. Jun 22, 2019
package.json Replace anye mention of eatdinkrva with starter. Jun 22, 2019
tsconfig.json Add typescript. Add node, react, and react-dom types (#2) May 25, 2019


Gatsby's Typescript Jest Starter

Barebones Gatsby starter with Typescript, Jest, and other useful configurations. A detailed guide on how to deploy your Gatsby site to AWS S3 buckets (manually and automatically) can be found in this readme.

This starter includes configurations for Typescript, Jest (ts-jest), EditorConfig, ESLint, Prettier, GitHub pull request templates, and even Gitlab-CI. Enjoy!


In addition to Gatsby's recommended pre-requisites, this starter suggests to do the following:

If you plan to use GitLab-CI as your CI tool, see Deploying Your Gatsby Site to an S3 Bucket.

Getting Started

  1. Create a Gatsby site.

    Use the Gatsby CLI to create a new site, specifying this starter.

    # create a new Gatsby site using this starter
    gatsby new my-gatsby-starter
  2. Start developing.

    Navigate into your new site’s directory and start it up.

    cd my-gatsby-starter/
    gatsby develop
  3. Open the source code and start editing!

    Your site is now running at http://localhost:8000!

    Note: You'll also see a second link: http://localhost:8000/___graphql. This is a tool you can use to experiment with querying your data. Learn more about using this tool in the Gatsby tutorial.

    Open the my-gatsby-starter directory in your code editor of choice and edit src/pages/index.js. Save your changes and the browser will update in real time!

Type-Checking and Linting

The package.json in this starter includes scripts for performing type-checking and linting on your project.

To check for correct typing run npm run type-check on the command line.

To check for correct code formatting with ESLint, run npm run lint on the command line.


Creating New Tests

One example test has been included in this starter. It can be found under /src/components/__tests__/header.tsx. This test creates a Header component and makes sure it renders correctly. Check out the Jest documentation for how to write more tests.

Running Tests

To run Jest tests on the project, run npm test on the command line.

Deploying Your Gatsby Site to an S3 Bucket

AWS S3 Bucket Set Up

AWS S3 buckets can be used to host Gatsby sites! You will need to create an S3 bucket for each development environment. If you would like to use a custom domain, the name of the bucket will need to match the URL of the environment. For example, if you own and would like your test environment to be, your bucket name must be

These instructions will dictate how to create buckets for 3 separate environments: staging, QA, and production. Replace <your_site_name> with your site URL that you own. If you do not want to use a custom domain registered with AWS's Route 53, the buckets can have any name.

  1. Create buckets named: dev.<your_site_name>.com, qa.<your_site_name>.com, and <your_site_name>.com in AWS S3.

  2. For each bucket, go to Permissions, then Bucket Policy.

  3. Paste the following into the text-field (remember to replace <BUCKET_NAME> with your bucket name):

    "Version": "2012-10-17",
    "Statement": [
            "Sid": "PublicReadForGetBucketObjects",
            "Effect": "Allow",
            "Principal": "*",
            "Action": "s3:GetObject",
            "Resource": "arn:aws:s3:::<BUCKET_NAME>/*"
  1. Click Save. If there is an error, go to Block public access and ensure that at least the two last options are off.

  2. Click the tab Properties. Click the box titled Static Web Hosting. Choose Use this bucket to host a website.

  3. In the Index document input, type index.html. In the Error document input, type 404.html. Click Save.

  4. Your buckets are all set up! In your bucket list, each bucket should be listed as Public.

Using a Custom Domain for Environments

These instructions will assume that your custom domain is registered in AWS's Route 53. If your domain is registered with another registrar, you will need to point your domain and any sub-domains to the appropriate bucket. The raw URL for each bucket can be found in the Static Web Hosting box mentioned in step 5 above.

  1. Go to Route 53 in AWS.

  2. Click Hosted Zones. Click the domain you wish to use for your site.

  3. Click the Create Record Set button. Type dev. into the Name: field.

  4. Choose Yes next to Alias:. Click the input next to Alias Target. A list of AWS services should show. Choose dev.<your_site_name>.com. Click Create.

  5. Repeat steps 3 and 4 for your other two environments.

  6. All done! Your domain has been pointed at your S3 buckets (environments).

Deploying to S3 Bucket Manually

While deploying manually is useful at first, it is highly recommended to set up Automated Deployments (which are covered in the next section).

  1. Run gatsby build on the command line.

  2. Navigate to the S3 bucket in AWS you would like to deploy your site to.

  3. Click Upload. Copy all of the files inside the /public folder generated by Gatsby. You can select all the files in your file browser and drag them to the prompt that opened when Upload was clicked.

  4. Navigate to your bucket URL (either a custom domain set up in the last section or the raw URL for the bucket) and see your Gatsby site!

Deploying to S3 Bucket Automatically with GitLab-CI

The .gitlab-ci.yml file will be used to automate site deployments using GitLab-CI. This file define three build stages: build, test, and deploy. Three environments are also included: staging, QA, and production. The stages and environments can be tailored to your project's needs.

  1. In .gitlab-ci.yml, replace any instance of <BUCKET_NAME> with the appropriate name.

  2. In AWS, set up a new user with permission to write to S3 buckets. At the end, make sure to save the user's AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY somewhere safe. You will not be able to view these again.

  3. Create a new project on GitLab. An existing repo using a different version control provider can also be mirrored. Note: GitLab can still be used for automated deployments even if your project uses a different version control provider (such as GitHub).

  4. In GitLab, navigate to the project you just created. Click Settings in the left-hand navigation bar. Click CI/CD in the sub-menu under Settings.

  5. Scroll down to the section titled Variables. This is where you'll set your credentials for AWS. Never put passwords or secrets directly in code. Create two keys, AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY. Paste the values you saved in step 2.

GitLab will now be able to upload your site to your S3 buckets. Descriptions of the environments are as follows:

  • Staging
    • Trigger: Push a change to a feature branch.
    • Description: Used for testing code prior to merging.
  • QA
    • Trigger: Merge a branch into master.
    • Description: Used for testing master before deploying to production
  • Production
    • Trigger: Creating a release tag of masterDev
    • Description: Main site where end-users will visit.

Project Structure

A quick look at the top-level files and directories you'll see in a Gatsby project using this starter.

├── __mocks__
├── .github
├── node_modules
├── src
├── .editorconfig
├── .eslintrc.js
├── .gitignore
├── .gitlab-ci.yml
├── .prettierrc
├── gatsby-browser.js
├── gatsby-config.js
├── gatsby-node.js
├── gatsby-ssr.js
├── jest-preprocess.js
├── jest.config.js
├── loadershim.js
├── package-lock.json
├── package.json
  1. /__mocks__: This directory contains manual mocks which are used to stub out functionality with mock data. For example, instead of accessing a remote resource like a website or a database, you might want to create a manual mock that allows you to use fake data. This ensures your tests will be fast and not flaky. This description can be found in the Jest documentation.

  2. /.github: This directory contains GitHub-specific files such as a pull request template ( or a contributing guide ( GitHub will automatically read and use these files.

  3. /node_modules: This directory contains all of the modules of code that your project depends on (npm packages). These packages are automatically installed when gatsby develop is run.

  4. /src: This directory will contain all of the code related to what you will see on the front-end of your site (what you see in the browser) such as your site header or a page template. src is a convention for “source code”.

  5. .editorconfig: This is a configuration file for EditorConfig. EditorConfig helps maintain consistent coding styles for multiple developers working on the same project across various editors and IDEs. It is recommended to download the EditorConfig extension for the IDE you will be using.

  6. .eslintrc.js: This is a configuration file for ESLint. ESLint is a linting tool for JavaScript. Code linting is a type of static analysis that is frequently used to find problematic patterns or code that doesn’t adhere to certain style guidelines. This description can be found in the ESLint documentation.

  7. .gitignore: This file tells git which files it should not track / not maintain a version history for.

  8. .gitlab-ci.yml: This file is optional. It should be deleted if you are not going to be using GitLab-CI for automated deployments. This is a configuration file for deploying your site with Gitlab-CI. This YAML file details stages for building, testing, and deploying your Gatsby site to an AWS S3 bucket using Gitlab-CI. See Deploying Your Gatsby Site to an S3 Bucket for more info.

  9. .prettierrc: This is a configuration file for Prettier. Prettier is a tool to help keep the formatting of your code consistent.

  10. gatsby-browser.js: This file is where Gatsby expects to find any usage of the Gatsby browser APIs (if any). These allow customization/extension of default Gatsby settings affecting the browser.

  11. gatsby-config.js: This is the main configuration file for a Gatsby site. This is where you can specify information about your site (metadata) like the site title and description, which Gatsby plugins you’d like to include, etc. (Check out the config docs for more detail).

  12. gatsby-node.js: This file is where Gatsby expects to find any usage of the Gatsby Node APIs (if any). These allow customization/extension of default Gatsby settings affecting pieces of the site build process.

  13. gatsby-ssr.js: This file is where Gatsby expects to find any usage of the Gatsby server-side rendering APIs (if any). These allow customization of default Gatsby settings affecting server-side rendering.

  14. jest-preprocess.js: This is a configuration file containing Babel settings for Jest. jest.config.js points to this file in order to transform all .tsx and jsx files that will be tested.

  15. jest.config.js: This is a configuration file for Jest. Jest is a JavaScript testing framework.

  16. LICENSE: Gatsby is licensed under the MIT license.

  17. loadershim.js: This file contains a function used by Jest when tests are run.

  18. package-lock.json (See package.json below, first). This is an automatically generated file based on the exact versions of your npm dependencies that were installed for your project. (You won’t change this file directly).

  19. package.json: A manifest file for Node.js projects, which includes things like metadata (the project’s name, author, etc). This manifest is how npm knows which packages to install for your project.

  20. A text file containing useful reference information about your project.

  21. tsconfig.json: This is a configuration file for Typescript. Typescript is a typed superset of JavaScript.

You can’t perform that action at this time.