preact-cli: Can't generate certificates on fresh install

@skdigital Sure, understood. As mentioned it’s not something we actually have control over. The best solution was to just get rid of it going forward. In the interim, you can just use any http server on the production directory. For example, I use sirv-cli for testing. There’s no HTTP/2 (yet) but the important part (imo) is to just get it up & running as a sanity check.

$ npm install -g sirv-cli
$ npm run build
$ sirv build --single

Thought you might be the most appropriate person talk about this, that’s why I assigned you

Not sure why I’m assigned. This wasn’t a smooth process for me either. Part of the reason why I’ve advocated to get rid of serve entirely for next release.

This is a permissions thing, and we’re totally at the mercy of what simplehttp2server is permitted to do.

My guess is that it has to do with how users’ machines have installed node and npm. Specifically, if sudo is granted to the installation or not. Since 99% of the reports here are Windows, I’m betting that’s the case.

Lol just noticed these issues have been going on for over a year, whats the problem, seems that this devCert thing is causing big issues for windows users. I dont have any of these issues with Nextjs or Reactjs, its just with Preact, I cant build and serve the production version.

I am running into this issue currently, nightmare, tried everything it seems with no luck.

My system:

Windows 10 64bit NVM with Node stable and 11x (on linux subsystem) Node 11x on Windows 10 Latest Preact CLI

I tried:

1. Yarn add simplehttp2servers (didnt work)
2. Tried yarn serve && NPM run serve with Windows Subsystem Linux Shell, Git Bash, Powershell, CMD, CMDr, HyperTerminal (with elevated admin and Sudo command. It fails everytime. Even after installing simplehttp2server locally and globally with both npm and yarn.

Steps to reproduce:

1. npm install -g preact-cli
2. preact create <app> --yarn || standard npm
3. cd <app>
4. yarn serve || npm run serve etc…

Result: yarn run v1.12.3 $ preact build --no-service-worker --template src/template.html && preact serve Setting up SSL certificate (may require sudo)… Attempting to spawn simplehttp2server to generate cert. Failed to generate dev SSL certificate: Error: spawn C:\Users\Sean Knowles\Desktop\Dev\preact\opsap-web\node_modules\simplehttp2server\vendor\simplehttp2server_windows_amd64.exe ENOENT Falling back to shared directory + simplehttp2server. (dir: C:\Users\Sean Knowles\AppData\Roaming\preact-cli)

server error> Error: spawn C:\Users\Sean Knowles\Desktop\Dev\preact\opsap-web\node_modules\simplehttp2server\vendor\simplehttp2server_windows_amd64.exe ENOENT Error: spawn C:\Users\Sean Knowles\Desktop\Dev\preact\opsap-web\node_modules\simplehttp2server\vendor\simplehttp2server_windows_amd64.exe ENOENT

error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

For the record, I had a similar issue but it wouldn’t even work within WSL or Git Bash.

Turned out npm install didn’t run simplehttp2server’s install script so the node_modules/simplehttp2server/vendor/simplehttp2server_windows_amd64.exe file really didn’t exist. A simple npm install --no-save simplehttp2server fixed it for me.