-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
▲ Something went wrong #51
Comments
Could you provide your node version? The CLI doesn't work with <=18 I believe. |
node --version |
Thanks! I'll be able to test soon and see what I find |
I meet same problem on ubuntu 24.04 , nodejs 20.
|
Thanks for reproducing! Would you be able to try that same command again? I've just pushed an update to |
|
Thanks! Looks like the request retrieving the most recent commit's sha isn't returning the correct value. Does this link work for you? api.github.com/repos/tommypop2/begit/commits?per_page=1 |
It will return 'API rate limit exceeded ' https://github.com/Tommypop2/begit/blob/71549357966bacfcc2a372f9d57c7b51b906b2a0/packages/core/src/utils.ts#L29 Add GITHUB_API_TOKEN to header will fix this issue https://docs.github.com/en/rest/authentication/authenticating-to-the-rest-api?apiVersion=2022-11-28 |
Ah, ok. Yeah I think I'll try using the to the |
@lakako I've just added support for the |
I’ve been seeing this “Something went wrong” error for a week at work. I’ve assumed it is to do with being behind a corporate proxy or a similar network/auth related issue, because that’s been an ongoing issue in various projects. However, those network and auth issues are resolved, yet “pnpm create solid” with all default options fails with “Something went wrong” consistently. Is there any way to turn on more verbose debugging or logging? I tried the curl mentioned above and it returns valid json. Thanks for any help! |
Run but run 'pnpm create solid@latest' still cause |
That's interesting. When I run the npx command I get a trace that ultimately complains about a self signed certificate in the chain. That's highly likely because of the corporate environment I'm in, however all other network activity is fine, including plain curl with no environment variables. Any ideas? |
I don't like it, but setting NODE_TLS_REJECT_UNAUTHORIZED=0 in the environment works around it. Unsettling because everything else works with ssl fine, but a way forward. I wonder if fetch is not using the machines certificate chain? |
OK, some success! The env var |
@lakako I've just released a new version of |
@aellerton Great things work now!! Do other CLI tools work properly with your setup without modification? I suspect it's where |
@Tommypop2 It works fine. Thank you. |
Closing this as everything seems to be resolved. |
Select Is this a Solid-Start project? — YES
The text was updated successfully, but these errors were encountered: