Skip to content

danielroe/telemetry

 
 

Repository files navigation

Nuxt Telemetry Module

ℹ️ Only used for Nuxt 2.13+

Nuxt.js collects anonymous telemetry data about general usage. This helps us to accurately gauge Nuxt feature usage and customization across all our users.

This program is optional. You will be asked on first time to get permission and you can always opt-out if you'd not like to share any information.

Why collecting Telemetry?

Nuxt.js has grown a lot from its initial release (7 Nov 2016) and we are keep listening to community feedback to improve it.

However, this manual process only collects feedback from a subset of users that takes the time to fill the issue template and it may have different needs or use-case than you.

Nuxt Telemetry collects anonymous telemetry data about general usage. This helps us to accurately gauge feature usage and customization across all our users. This data will let us better understand how Nuxt.js is used globally, measuring improvements made (DX and performances) and their relevance.

Events

We collect multiple events:

  • Command invoked (nuxt dev, nuxt build, etc)
  • Versions of Nuxt.js and Node.js
  • General machine informations (MacOS/Linux/Windows and if command is run within CI, ci name)
  • Duration of the Webpack build and average size of the application, as well as the generation stats (when using nuxt generate or nuxt export)
  • What are the public dependency of your project (Nuxt modules)

You can see the list of events in lib/events.

Example of an event:

{
   "name": "NUXT_PROJECT",
   "payload": {
    "type": "GIT",
    "isSSR": true,
    "target": "server",
    "isTypescriptBuild": false,
    "isTypescriptRuntime": false,
    "isProgrammatic": false,
    "packageManager": "npm"
   }
}

To display the exact data that will be sent, you can use NUXT_TELEMETRY_DEBUG=1.

Sensitive data

We take your privacy and our security very seriously.

We do not collect any metrics which may contain sensitive data.

This includes, but is not limited to: environment variables, file paths, contents of files, logs, or serialized JavaScript errors.

The data we collect is completely anonymous, not traceable to the source (using hash+seed), and only meaningful in aggregate form. No data we collect is personally identifiable or trackable.

Opting-out

You can disable Nuxt Telemetry for your project with several ways:

  1. Setting telemetry: false in your nuxt.config:
export default {
  telemetry: false
}
  1. Using an environment variable:
NUXT_TELEMETRY_DISABLED=1
  1. Using npx nuxt telemetry disable
npx nuxt telemetry [status|enable|disable] [-g,--global] [dir]

Skip Prompt

If you encounter problems with consent prompt, and want to participate without asking this question, you can set telemetry: true from nuxt.config:

export default {
  telemetry: true
}

Thank you

We want to thank you for participating in this telemetry program to help us better understand how you use Nuxt.js to keep improving it 💚

License

MIT License

Copyright (c) NuxtJS Team

About

Nuxt Telemetry

Resources

License

Code of conduct

Stars

Watchers

Forks

Sponsor this project

 

Packages

No packages published

Languages

  • TypeScript 99.0%
  • Other 1.0%