rsnext/examples/with-sentry
Joe Haddad 7d038dfef1
Suggest npx over npm init (#13637)
This updates old examples to the more universal `npx` command.

Fixes https://github.com/vercel/next.js/discussions/12103
2020-06-01 17:36:57 +00:00
..
pages refactor(with-sentry): example (#13434) 2020-05-27 16:11:46 +00:00
utils Upgrade to Prettier 2 (#13061) 2020-05-18 15:24:37 -04:00
next.config.js Improve linting rules to catch more errors (#9374) 2019-11-10 19:24:53 -08:00
package.json refactor(with-sentry): example (#13434) 2020-05-27 16:11:46 +00:00
README.md Suggest npx over npm init (#13637) 2020-06-01 17:36:57 +00:00
server.js Upgrade to Prettier 2 (#13061) 2020-05-18 15:24:37 -04:00

Sentry example

An example showing use of Sentry to catch & report errors on both client + server side.

How to use

Using create-next-app

Execute create-next-app with npm or Yarn to bootstrap the example:

npx create-next-app --example with-sentry with-sentry-app
# or
yarn create next-app --example with-sentry with-sentry-app

Download manually

Download the example:

Install it and run:

npm

npm install
npm run dev

yarn

yarn
yarn dev

Deploy it to the cloud with Vercel (Documentation).

Configuration

You will need a Sentry DSN for your project. You can get it from the Settings of your Project, in Client Keys (DSN), and copy the string labeled DSN (Public).

The Sentry DSN should then be added as an environment variable when running the dev, build, and start scripts in package.json:

{
  "scripts": {
    "dev": "SENTRY_DSN=<dsn> node server.js",
    "build": "SENTRY_DSN=<dsn> next build",
    "start": "SENTRY_DSN=<dsn> NODE_ENV=production node server.js"
  }
}

Note: Setting environment variables in a package.json is not secure, it is done here only for demo purposes. See the with-dotenv example for an example of how to set environment variables safely.