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 npx next telemetry disable output where the preference setting was saved to #31241

Closed
binary64 opened this issue Nov 10, 2021 · 1 comment · Fixed by #31305
Closed

Make npx next telemetry disable output where the preference setting was saved to #31241

binary64 opened this issue Nov 10, 2021 · 1 comment · Fixed by #31305

Comments

@binary64
Copy link

Describe the feature you'd like to request

For this message:

$ npx next telemetry disable
Your preference has been saved.

Status: Disabled

You have opted-out of Next.js' anonymous telemetry program.
No data will be collected from your machine.
Learn more: https://nextjs.org/telemetry

I find it unsettling to see there were no changes in my git repo.

Describe the solution you'd like

Instead of Your preference has been saved. it would be lovely to see it say something like Your preference has been saved to /home/user/somethingsomething

Describe alternatives you've considered

Using sysinternals
@timneutkens timneutkens mentioned this issue Nov 11, 2021
Merged
10 tasks
timneutkens added a commit to timneutkens/next.js that referenced this issue Nov 11, 2021
@timneutkens
Output where preference is saved
96910d6 
Fixes vercel#31241
@kodiakhq kodiakhq bot closed this as completed in #31305 Nov 11, 2021
kodiakhq bot pushed a commit that referenced this issue Nov 11, 2021
@timneutkens
Output where preference is saved (#31305)
c4558c9 
Fixes #31241



## Bug

- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [ ] Errors have helpful link attached, see `contributing.md`

## Feature

- [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR.
- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [ ] Documentation added
- [ ] Telemetry added. In case of a feature if it's used or not.
- [ ] Errors have helpful link attached, see `contributing.md`

## Documentation / Examples

- [ ] Make sure the linting passes by running `yarn lint`
@balazsorban44
Copy link
Member

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@vercel vercel locked as resolved and limited conversation to collaborators Jan 27, 2022
natew pushed a commit to natew/next.js that referenced this issue Feb 16, 2022
@timneutkens @natew
Output where preference is saved (vercel#31305)
3f65193 
Fixes vercel#31241



## Bug

- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [ ] Errors have helpful link attached, see `contributing.md`

## Feature

- [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR.
- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [ ] Documentation added
- [ ] Telemetry added. In case of a feature if it's used or not.
- [ ] Errors have helpful link attached, see `contributing.md`

## Documentation / Examples

- [ ] Make sure the linting passes by running `yarn lint`
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Output where preference is saved timneutkens/next.js
2 participants
@binary64 @balazsorban44