|
|
|
|
|
by kodablah
2869 days ago
|
|
> it would do extra stuff like adding it to the Windows cert store if you're there, adding it to Firefox if you use it, etc This is what mkcert does (FF on Windows not done yet, but FF everywhere else and OS root store is). > And being package it's better to collaborate on than everyone making their own process (and possibly screwing it up) Not sure the difference between it being an npm package or a Go project on GitHub is that large. Or are you saying "go build" is easier to screw up than "npm install"? EDIT: My mistake, misunderstood the context of the comment. |
|
> Not sure the difference between it being an npm package or a Go project on GitHub is that large.
I know mkcert also does this. I also agree that other maintained projects are good too. My comment was in response was to it's parent, which reads:
> So you could use openssl commands and have actually less installation requirements.