Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

make providers headlines so they become linkable #11613

Merged
merged 1 commit into from
Apr 3, 2020
Merged

make providers headlines so they become linkable #11613

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 10 additions & 10 deletions errors/no-cache.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
# No Cache Detected

#### Why This Error Occurred
### Why This Error Occurred

A Next.js build was triggered in a continuous integration environment, but no cache was detected.

This results in slower builds and can hurt Next.js' persistent caching of client-side bundles across builds.

#### Possible Ways to Fix It
### Possible Ways to Fix It

> **Note**: If this is a new project, or being built for the first time in your CI, you can ignore this error.
> However, you'll want to make sure it doesn't continue to happen and fix it if it does!
Expand All @@ -15,11 +15,11 @@ Configure Next.js' cache to be persisted across builds. Next.js stores its cache

Storing this folder across builds varies by CI provider. We've provided a list of a few common providers below.

**ZEIT Now**
#### ZEIT Now

Next.js caching is automatically configured for you. There's no action required on your part.

**CircleCI**
#### CircleCI

Edit your `save_cache` step in `.circleci/config.yml` to include `.next/cache`:

Expand All @@ -34,7 +34,7 @@ steps:

If you do not have a `save_cache` key, please follow CircleCI's [documentation on setting up build caching](https://circleci.com/docs/2.0/caching/).

**Travis CI**
#### Travis CI

Add or merge the following into your `.travis.yml`:

Expand All @@ -46,7 +46,7 @@ cache:
- .next/cache
```

**GitLab CI**
#### GitLab CI

Add or merge the following into your `.gitlab-ci.yml`:

Expand All @@ -58,13 +58,13 @@ cache:
- .next/cache/
```

**Netlify CI**
#### Netlify CI

It is **not possible** to cache custom build files on Netlify. Please contact their support and request they support this behavior.

You can investigate using a 3rd party solution (e.g. [`cache-me-outside`](https://github.com/DavidWells/cache-me-outside)) to manually cache the Next.js output.

**AWS CodeBuild**
#### AWS CodeBuild

Add (or merge in) the following to your `buildspec.yml`:

Expand All @@ -75,7 +75,7 @@ cache:
- '.next/cache/**/*' # Cache Next.js for faster application rebuilds
```

**GitHub Actions**
#### GitHub Actions

Using GitHub's [actions/cache](https://github.com/actions/cache), add the following step in your workflow file:

Expand All @@ -86,7 +86,7 @@ with:
key: ${{ runner.os }}-nextjs-${{ hashFiles('**/package-lock.json') }}
```

**Bitbucket Pipelines**
#### Bitbucket Pipelines

Add or merge the following into your `bitbucket-pipelines.yml` at the top level (same level as `pipelines`):

Expand Down