Hello! We attempted to test codeorb today and ran into a few installation and execution hurdles that prevent the project from running out-of-the-box:
1. NPM Registry 404
Running the documented command npx -y codeorb fails with a 404 error:
npm error 404 'codeorb@latest' is not in this registry.
2. Build script fails on Vite
Attempting to install directly from the repository (npm install -g github:ethanplusai/codeorb) fails during the postinstall hook. The script tries to run vite build in src/frontend, but vite is not found (sh: 1: vite: not found). Because vite is listed in devDependencies of the frontend package.json, a global install does not reliably resolve it for the build step.
3. Scanner finds 0 files
After manually cloning the repo, compiling the frontend assets, and starting the server via node bin/cli.js, the scanner successfully launched but reported Found 0 files / 0 dependencies when pointed to a standard project directory. It appears the scanner might have issues parsing certain .gitignore configurations or hidden directories.
Hope this feedback helps improve the initial setup flow!
(Issue identified and reported on behalf of @plocemourasouza)
Hello! We attempted to test
codeorbtoday and ran into a few installation and execution hurdles that prevent the project from running out-of-the-box:1. NPM Registry 404
Running the documented command
npx -y codeorbfails with a 404 error:npm error 404 'codeorb@latest' is not in this registry.2. Build script fails on Vite
Attempting to install directly from the repository (
npm install -g github:ethanplusai/codeorb) fails during thepostinstallhook. The script tries to runvite buildinsrc/frontend, butviteis not found (sh: 1: vite: not found). Becauseviteis listed indevDependenciesof the frontendpackage.json, a global install does not reliably resolve it for the build step.3. Scanner finds 0 files
After manually cloning the repo, compiling the frontend assets, and starting the server via
node bin/cli.js, the scanner successfully launched but reportedFound 0 files / 0 dependencieswhen pointed to a standard project directory. It appears the scanner might have issues parsing certain.gitignoreconfigurations or hidden directories.Hope this feedback helps improve the initial setup flow!
(Issue identified and reported on behalf of @plocemourasouza)