Describe the feature
When using self-signed generated certificates for local development, every time you restart listhen (or in my case restart the nuxt dev server), a new certificate is generated and your browser's "Your connection is not private" page must be explicitly bypassed.
As a small optimization, it would be very nice if the generated certificates were (maybe optionally) persisted to disk so that you only need to manually bypass the browser's insecure warning page once (or each time a new certificate is generated). This is similar to how @vitejs/plugin-basic-ssl works by saving the cert inside of a hidden temp dir in your project's node_modules directory (./node_modules/.vite/basic-ssl).
I could see listhen doing something similar by persisting the certs at ./node_modules/.listhen/certs.
I'm not sure if this has security implications or may be unreliable depending on the runtime environment, so if this is impractical and/or unadvisable I completely understand. Thanks!
Additional information
Describe the feature
When using self-signed generated certificates for local development, every time you restart listhen (or in my case restart the nuxt dev server), a new certificate is generated and your browser's "Your connection is not private" page must be explicitly bypassed.
As a small optimization, it would be very nice if the generated certificates were (maybe optionally) persisted to disk so that you only need to manually bypass the browser's insecure warning page once (or each time a new certificate is generated). This is similar to how @vitejs/plugin-basic-ssl works by saving the cert inside of a hidden temp dir in your project's
node_modulesdirectory (./node_modules/.vite/basic-ssl).I could see listhen doing something similar by persisting the certs at
./node_modules/.listhen/certs.I'm not sure if this has security implications or may be unreliable depending on the runtime environment, so if this is impractical and/or unadvisable I completely understand. Thanks!
Additional information