Pushed chore(deps): update devdependency @nuxtjs/eslint-config-typescript to v4 (#241) Co-authored-by: Renovate Bot <[email protected]> (fe1c8d5)

Pushed maintenance(deps): update Sentry from 5.23.0 to 5.27.0 (#237) Also, update dev dependencies. Co-authored-by: Renovate Bot <[email protected]> (3baab5d)

Pushed chore: release 4.3.5 (9637d35)

Pushed chore(deps): update devdependency @types/jest to ^26.0.14 (#234) Co-authored-by: Renovate Bot <[email protected]> (f772f07)

Pushed chore: use github CI and update/add bug templates (#236) Also fix some lint issues (485553e)

Pushed chore: use github CI and update/add bug templates Also fix some lint issues (4383508)

Pushed fix: initialize server-side Sentry when using Nuxt programmatically (#235) Switched from "listen" to "ready" hook so that server-side Sentry is also initialized when starting Nuxt programmatically from within a server framework like expressjs. The side effect of using "ready" hook is that Sentry will also be initialized on building which seems like an OK thing to do. Also, in a typical case, "ready" triggers before "listen" which should actually be better as it would also catch issues with starting server listener. Resolves #230 (575e4db)

Pushed fix: initialize server-side Sentry when using Nuxt programmatically Switched from "listen" to "ready" hook so that server-side Sentry is also initialized when starting Nuxt programmatically from within a server framework like expressjs. The side effect of using "ready" hook is that Sentry will also be initialized on building which seems like an OK thing to do. Also, in a typical case, "ready" triggers before "listen" which should actually be better as it would also catch issues with starting server listener. Resolves #230 (f6f22ce)

Pushed fix: initialize server-side Sentry when using Nuxt programmatically Switched from "listen" to "ready" hook so that server-side Sentry is also initialized when starting Nuxt programmatically from within a server framework like expressjs. The side effect of using "ready" hook is that Sentry will also be initialized on building which seems like an OK thing to do. Also, in a typical case, "ready" triggers before "listen" which should actually be better as it would also catch issues with starting server listener. Resolves #230 (a86cbeb)

Pushed chore(deps): bump node-fetch from 2.6.0 to 2.6.1 (#229) Bumps [node-fetch](https://github.com/bitinn/node-fetch) from 2.6.0 to 2.6.1. - [Release notes](https://github.com/bitinn/node-fetch/releases) - [Changelog](https://github.com/node-fetch/node-fetch/blob/master/docs/CHANGELOG.md) - [Commits](https://github.com/bitinn/node-fetch/compare/v2.6.0...v2.6.1) Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> (ed1c55f)

Pushed fix(deps): update Sentry dependency from 5.20.1 to 5.23.0 (#223) Also, update other dependencies. Co-authored-by: Renovate Bot <[email protected]> (9894b02)

Pushed chore(deps): update devdependency @release-it/conventional-changelog to v2 (#228) Co-authored-by: Renovate Bot <[email protected]> (7d0445e)

Pushed chore(deps): update devdependency release-it to v14 (#227) Co-authored-by: Renovate Bot <[email protected]> (8b9141a)