Skip to content
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

Koyeb failure to deploy, vercel displaying code instead of webUI. #75

Open
efwxx opened this issue Aug 10, 2024 · 7 comments
Open

Koyeb failure to deploy, vercel displaying code instead of webUI. #75

efwxx opened this issue Aug 10, 2024 · 7 comments
Assignees

Comments

@efwxx
Copy link

efwxx commented Aug 10, 2024

Issues named in title, koyeb error log:

======== Output: heroku/nodejs-corepack@2.6.2 ========
[Error: heroku/nodejs-corepack package.json error]
There was an error while attempting to parse this project's
package.json file. Please make sure it is present and properly
formatted.
Details: Could not parse package.json. Failed to parse version. at line 3 column 24
err:  heroku/nodejs-corepack@2.6.2 (1)
3 of 4 buildpacks participating
heroku/nodejs-engine       2.6.2
heroku/nodejs-pnpm-engine  2.6.2
heroku/nodejs-pnpm-install 2.6.2
[Heroku Node.js Engine Buildpack]
[Checking Node.js version]
[Error: Node.js engine package.json error]
Couldn't parse package.json: Could not parse package.json. Failed to parse version. at line 3 column 24
ERROR: failed to build: exit status 1
exit status 51
Layer cache not found

Vercel issue displayed in screenshot below:
image

@efwxx
Copy link
Author

efwxx commented Aug 11, 2024

nothing was modified in deployment for koyeb other than the location (changed from frankfurt -> washington), and nothing was modified for the vercel deployment. I attempted to change the port in the code for vercel:

const port = parseInt("8000");

any help would be appreciated <3

@Notplayingallday383 Notplayingallday383 self-assigned this Aug 12, 2024
@Notplayingallday383
Copy link
Member

hi there, I dont know what could be causing the issue with koyeb, as for vercel could you send me the deployment settings you used to deploy itu?

@efwxx
Copy link
Author

efwxx commented Aug 12, 2024

unsure if this is what you're asking for, but i'll provide it regardless. image

@efwxx
Copy link
Author

efwxx commented Aug 12, 2024

I didn't really modify anything at deployment, I simply clicked on the deploy to Vercel button on the readme, cloned it to a private repository and had Vercel deploy everything on its own.
image

@88411
Copy link

88411 commented Oct 10, 2024

Same happening to me

@88411
Copy link

88411 commented Oct 10, 2024

I found an alternative that actually works: Cloudflare

  1. First fork this repo
  2. Then go to Cloudflare.com and sign in
  3. Then on the left column select workers and pages
  4. After that click on create and then select pages (NOT workers)
  5. Select connect to git and connect your GitHub account.
  6. Then select the forked repo and click begin setup.

These next steps are very important:

DO NOT touch framework preset.

  1. For the build commands, type: "npm install" (The repo says to put "npm install && npm start" however this does not work)
  2. For output directory type: "static"
  3. Then click save and deploy and cross your fingers that everything goes well

After it builds it will provide you with a link and your good to go.

Also if for some reason you can't figure it out here is my link I got from following those exact steps
"https://webos2-d9d.pages.dev/"

By the time you are reading this it might be blocked tho idk

GL

@shonnyy
Copy link

shonnyy commented Nov 6, 2024

Set the output directory to static in your Project Settings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants