Skip to content

Latest commit

 

History

History
266 lines (213 loc) · 6.23 KB

gatsby-config.md

File metadata and controls

266 lines (213 loc) · 6.23 KB
Raw
title
Gatsby Config

Site configuration options for a Gatsby site are placed in a file at the root of the project folder called gatsby-config.js.

Note: There are many sample configs which may be helpful to reference in the different Gatsby Example Websites.

Configuration options

Options available to set within gatsby-config.js include:

  1. siteMetadata (object)
  2. plugins (array)
  3. pathPrefix (string)
  4. polyfill (boolean)
  5. mapping (object)
  6. proxy (object)
  7. developMiddleware (function)

siteMetadata

When you want to reuse common pieces of data across the site (for example, your site title), you can store that data in siteMetadata:

module.exports = {
  siteMetadata: {
    title: `Gatsby`,
    siteUrl: `https://www.gatsbyjs.org`,
    description: `Blazing fast modern site generator for React`,
  },
}

This way you can store it in one place, and pull it whenever you need it. If you ever need to update the info, you only have to change it here.

See a fuller description and sample usage in Gatsby.js Tutorial Part Four.

Plugins

Plugins are Node.js packages that implement Gatsby APIs. The config file accepts an array of plugins. Some plugins may need only to be listed by name, while others may take options (see the docs for individual plugins).

module.exports = {
  plugins: [
    `gatsby-plugin-react-helmet`,
    {
      resolve: `gatsby-source-filesystem`,
      options: {
        name: `docs`,
        path: `${__dirname}/../docs/`,
      },
    },
  ],
}

See more about Plugins for more on utilizing plugins, and to see available official and community plugins.

pathPrefix

It's common for sites to be hosted somewhere other than the root of their domain. Say we have a Gatsby site at example.com/blog/. In this case, we would need a prefix (/blog) added to all paths on the site.

module.exports = {
  // Note: it must *not* have a trailing slash.
  pathPrefix: `/blog`,
}

See more about Adding a Path Prefix.

Polyfill

Gatsby uses the ES6 Promise API. Because some browsers don't support this, Gatsby includes a Promise polyfill by default.

If you'd like to provide your own Promise polyfill, you can set polyfill to false.

module.exports = {
  polyfill: false,
}

See more about Browser Support in Gatsby.

Mapping node types

Gatsby includes an advanced feature that lets you create "mappings" between node types.

For instance, imagine you have a multi-author markdown blog where you want to "link" from each blog post to the author information stored in a yaml file named author.yaml:

---
title: A blog post
author: Kyle Mathews
---

A treatise on the efficacy of bezoar for treating agricultural pesticide poisoning.

author.yaml

- id: Kyle Mathews
  bio: Founder @ GatsbyJS. Likes tech, reading/writing, founding things. Blogs at bricolage.io.
  twitter: "@kylemathews"

You can map between the author field in frontmatter to the id in the author.yaml objects by adding to your gatsby-config.js:

module.exports = {
  plugins: [...],
  mapping: {
    "MarkdownRemark.frontmatter.author": `AuthorYaml`,
  },
}

Gatsby then uses this mapping when creating the GraphQL schema to enable you to query data from both sources:

query($slug: String!) {
  markdownRemark(fields: { slug: { eq: $slug } }) {
    html
    fields {
      slug
    }
    frontmatter {
      title
      author {
        # This now links to the author object
        id
        bio
        twitter
      }
    }
  }
}

Mapping can also be used to map an array of ids to any other collection of data. For example, if you have two JSON files experience.json and tech.json as follows:

// experience.json
[
  {
    "id": "companyA",
    "company": "Company A",
    "position": "Unicorn Developer",
    "from": "Dec 2016",
    "to": "Present",
    "items": [
      {
        "label": "Responsibility",
        "description": "Being an unicorn"
      },
      {
        "label": "Hands on",
        "tech": ["REACT", "NODE"]
      }
    ]
  }
]
// tech.json
[
  {
    "id": "REACT",
    "icon": "facebook",
    "color": "teal",
    "label": "React"
  },
  {
    "id": "NODE",
    "icon": "server",
    "color": "green",
    "label": "NodeJS"
  }
]

And then add the following rule to your gatsby-config.js:

module.exports = {
  plugins: [...],
  mapping: {
    'ExperienceJson.items.tech': `TechJson`
  },
}

You can query the tech object via the referred ids in experience:

query {
  experience: allExperienceJson {
    edges {
      node {
        company
        position
        from
        to
        items {
          label
          description
          link
          tech {
            label
            color
            icon
          }
        }
      }
    }
  }
}

Mapping also works between Markdown files. For example, instead of having all authors in a YAML file, you could have info about each author in a separate Markdown file:

---
author_id: Kyle Mathews
twitter: "@kylemathews"
---

Founder @ GatsbyJS. Likes tech, reading/writing, founding things. Blogs at bricolage.io.

And then add the following rule to your gatsby-config.js:

module.exports = {
  plugins: [...],
  mapping: {
    'MarkdownRemark.frontmatter.author': `MarkdownRemark.frontmatter.author_id`
  },
}

Similarly to YAML and JSON files, mapping between Markdown files can also be used to map an array of ids.

Proxy

Setting the proxy config option will tell the develop server to proxy any unknown requests to your specified server. For example:

module.exports = {
  proxy: {
    prefix: "/api",
    url: "http://examplesite.com/api/",
  },
}

See more about Proxying API Requests in Develop.

Advanced proxying with developMiddleware

See more about adding develop middleware.