You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not sure how webpack-dev-server uses this module or if they change something.
In my own projects and for this scenario of a dev server I generally spawn mkcert.
when you setup mkcert for the first time, it will generate a CA root for your own use and add it to every chain (macos, chrome, firefox, etc). From there, everytime you generate a certificate it is automatically trusted everywhere.
Using this from webpack-dev-server, I wonder why Chrome doesn't complain about the validity of the cert?
The text was updated successfully, but these errors were encountered: