rsnext/examples/with-sentry
2019-07-26 14:51:47 -05:00
..
pages form handler example: Update deps and fix build from dep update (#6732) 2019-03-27 16:12:45 -04:00
utils Add back in second line of comment (#7718) 2019-07-01 11:08:55 -04:00
next.config.js [with-sentry] Use env config instead of webpack where possible (#6381) 2019-02-21 00:33:32 +01:00
package.json Update Sentry to v5 and add @sentry/integrations (#6873) 2019-04-03 12:32:36 +02:00
README.md Remove deploy to now button from all examples (#7101) 2019-05-27 12:22:05 -07:00
server.js Docs: Fix comments in with-sentry example (server.js) (#8125) 2019-07-26 14:51:47 -05:00

Sentry example

How to use

Using create-next-app

Execute create-next-app with Yarn or npx 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 now (download)

now

About example

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

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.