vercel/next.js

Sudo on --experimental-https usage

MathiasGruber opened this issue · 0 comments

Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/reverent-paper-zxjmnv

To Reproduce

Run bun dev --experimental-https in any project

Current vs. Expected behavior

Current:

Sudo password:```

Expected:
No requirement for sudo in terms of generating certificates. 

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: arm64
  Version: #1 SMP Thu Oct 24 19:28:55 UTC 2024
  Available memory (MB): 48093
  Available CPU cores: 10
Binaries:
  Node: 20.10.0
  npm: 10.2.3
  Yarn: N/A
  pnpm: 8.11.0
Relevant Packages:
  next: 15.1.0 // There is a newer version (15.1.1) available, upgrade recommended! 
  eslint-config-next: 15.1.0
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.2

Which area(s) are affected? (Select all that apply)

Runtime, Turbopack, Webpack

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

I don't believe it should be a requirement to have sudo for creating certificates and running experiment-https?