My Install Failed. What Should I Do? #1052
Replies: 7 comments 16 replies
-
|
Tested this on Manjaro and it worked perfectly, in the end. I just needed to cleanup all the directories that the AppImage attempted to create on install (not sure which one caused the issue though) and then re-run the Thanks for the solution! 🙂 |
Beta Was this translation helpful? Give feedback.
-
|
it worked on Fedora 37 without problems. I can run |
Beta Was this translation helpful? Give feedback.
-
|
Installation with this package worked on Ubuntu 22.10. No errors. The The only command that works its the |
Beta Was this translation helpful? Give feedback.
-
|
After kit seemingly failed to install (All UI just a black box, opening devtools showed errors @johnlindquist/install-kit log outputChecking the content of |
Beta Was this translation helpful? Give feedback.
-
|
I'm getting an error on setup using Ubuntu 22.04 x64 |
Beta Was this translation helpful? Give feedback.
-
Got this loooooooooooong error while running the npx cmdcode: 'ERR_BAD_REQUEST', \r\n' + \r\n' +' Whoa there!\r\n' +' You have sent an invalid request. ' \r\n' + ' ' \r\n' + '\r\n' } } Node.js v18.12.1 |
Beta Was this translation helpful? Give feedback.
-
|
Hello. I am using NodeJS 22 version. And i cannot setup script kit. I have got this error |
Beta Was this translation helpful? Give feedback.



Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
My Install Failed. What Should I Do?
99.9% errors come from the SDK failing to install. To manually installed the SDK:
GitHub CLI
or Git
This builds the SDK to ~/.kit
Then open the app
More Details on the Install Process
The 3 Required Directories
1.
~/.kitThis is the Kit SDK. You should be able to download the SDK and extract it here. (This is also what
npm run buildtries to build)https://github.com/johnlindquist/kitapp/releases/latest
You should extract it so the package.json resides here:
~/.kit/package.json2.
~/.kenvThis is the Kit Environent where scripts are stored. It's simply a way to organize scripts, logs, tmp, etc. You can clone it from:
https://github.com/johnlindquist/kenv
You should clone it so the package.json resides here:
~/.kenv/package.json3.
~/.knodeThis is a version of node (v18.15.0) that matches the current version of the app.
https://nodejs.org/download/release/v18.15.0/
nodeshould be accessible as~/.knode/bin/nodeFinal Configuration Setups
Intall
esbuildfor TypeScript supportUse the .knode version of node to install esbuild into the ~/.kit dir:
Run the setup scripts
Thoughts on the Setup Process
esbuildis a different binary per-platform. It's been a challenge to get the CI process bundling the correct version and fighting against code-signing of unsign binaries. I an not an expert in this area.~/.kitand~/.knodeSDK outside of the app makes it possible to run scripts from the terminal and allows users to play with the SDK code before submitting PRs. It would be much easier to package it in the app, but we'd lose features.Beta Was this translation helpful? Give feedback.
All reactions