search

EddieHubCommunity / BioDrop

Connect to your audience with a single link. Showcase the content you create and your projects in one place. Make it easier for people to find, follow and subscribe.
https://biodrop.io
MIT License
5.73k stars 3.96k forks source link

Vercel Deployment Error : Failed to compile #1906

Closed solucompme closed 1 year ago

solucompme commented 1 year ago

Description

Hi ! I tried to deploy a second instance of LinkTree on Vercel. I deployed one last week without any issues and I did the same way for the second one, because when I tried to update the profiles data, it suddently stop updating and each deployment shows errors.

This is the log I got from the deployment screen on vercel

[15:15:09.585] Cloning github.com/MYACCOUNTPATH (I hide it for security purposes) [15:15:10.245] Cloning completed: 659.522ms [15:15:10.731] No Build Cache available [15:15:10.768] Running "vercel build" [15:15:11.262] Vercel CLI 28.4.6 [15:15:11.555] Installing dependencies... [15:15:24.622] npm WARN deprecated stable@0.1.8: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility [15:15:24.939] npm WARN deprecated source-map-resolve@0.6.0: See https://github.com/lydell/source-map-resolve#deprecated [15:15:25.821] npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. [15:15:31.407] npm WARN deprecated svgo@1.3.2: This SVGO version is no longer supported. Upgrade to v2.x.x. [15:15:32.779] npm WARN deprecated gherkin@5.1.0: This package is now published under @cucumber/gherkin [15:15:34.630] npm WARN deprecated cucumber-expressions@6.6.2: This package is now published under @cucumber/cucumber-expressions [15:15:40.299] npm WARN deprecated cucumber-expressions@5.0.18: This package is now published under @cucumber/cucumber-expressions [15:15:40.617] npm WARN deprecated cucumber@4.2.1: Cucumber is publishing new releases under @cucumber/cucumber [15:15:44.182] npm WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js. [15:16:03.262] [15:16:03.262] > linkfree@0.76.7 prepare [15:16:03.262] > husky install [15:16:03.262] [15:16:03.328] husky - Git hooks installed [15:16:03.357] [15:16:03.357] added 1826 packages in 51s [15:16:03.357] [15:16:03.357] 235 packages are looking for funding [15:16:03.357] run npm fund for details [15:16:04.731] Creating an optimized production build... [15:16:29.559] Failed to compile. [15:16:29.559] [15:16:29.559] [eslint] Failed to load config "react-app" to extend from. [15:16:29.559] Referenced from: /vercel/path0/package.json [15:16:29.560] [15:16:29.560] [15:16:29.622] Error: Command "react-scripts build" exited with 1

Screenshots

No response

Additional information

No response

github-actions[bot] commented 1 year ago

It's great having you contribute to this project

Welcome to the community :nerd_face:

If you would like to continue contributing to open source and would like to do it with an awesome inclusive community, you should join our Discord chat and our GitHub Organisation - we help and encourage each other to contribute to open source little and often 🤓 . Any questions let us know.

EmmaDawsonDev commented 1 year ago

Could this be due to the github action/vercel outage that happened earlier today?

solucompme commented 1 year ago

No I got this issue since last week with my first deployment. (I was able to make changes and update to files and suddently after I modified a name in a profile file, every deployments failed with the same error log.)

I fork a new repository in my github account from this repository (without any change) (EddyJouade Community) start a second deployment and still have the exact same error log.

EmmaDawsonDev commented 1 year ago

Did you follow the instructions for single user mode? https://github.com/EddieHubCommunity/LinkFree#single-user-mode

solucompme commented 1 year ago

Did you follow the instructions for single user mode? https://github.com/EddieHubCommunity/LinkFree#single-user-mode

No since it's not a single user usage

eddiejaoude commented 1 year ago

Not sure I understand what you are trying to do here @solucompme ?

[15:15:09.585] Cloning github.com/MYACCOUNTPATH (I hide it for security purposes)

Also why is this more secure? Does this mean you have more than 1 GitHub account?

eddiejaoude commented 1 year ago

Closing as no activity for 4 weeks