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

Vercel build keeps failing #132

Closed
AloisSeckar opened this issue Apr 2, 2024 · 7 comments
Closed

Vercel build keeps failing #132

AloisSeckar opened this issue Apr 2, 2024 · 7 comments
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@AloisSeckar
Copy link
Contributor

When ryu-cho creates pull request, the automated Vercel build always fails for some reason (eg. here).

There are links to failed build, but I don't have Vercel account yet to see them. Should I create one to investigate further, or can someone check what's wrong?

@AloisSeckar AloisSeckar added bug Something isn't working help wanted Extra attention is needed labels Apr 2, 2024
@AloisSeckar AloisSeckar changed the title Vercel preview build always failed Vercel preview build always fails Apr 2, 2024
@AloisSeckar AloisSeckar changed the title Vercel preview build always fails Vercel build keeps failing May 4, 2024
@AloisSeckar
Copy link
Contributor Author

I just realized it is not only preview builds that fail, but also all the production ones. For last couple of weeks, the changed I am regulary making do not appear on the live website. Czech docs are stuck and outdated now 😢 Noone noticed yet tho...

I tried to check Vercel deplyment log, but apparently I have no permission to see it (I created an account via my GitHub)

@Jinjiang can you help or point me out where to find help, please? 🙏

@Jinjiang
Copy link
Member

Jinjiang commented May 6, 2024

@AloisSeckar let me check

@Jinjiang
Copy link
Member

Jinjiang commented May 6, 2024

Here attached the error log first:

04:29:59.983 | x Build failed in 13.48s
04:29:59.983 | ✖ building client + server bundles...
04:29:59.990 | build error:
04:29:59.990 | Error: [vitepress] 1 dead link(s) found.
04:29:59.990 | at Object.renderStart (file:///vercel/path0/node_modules/.pnpm/[email protected]_@[email protected][email protected]/node_modules/vitepress/dist/node/serve-CXVdC751.js:42420:15)
04:29:59.990 | at file:///vercel/path0/node_modules/.pnpm/[email protected]/node_modules/rollup/dist/es/shared/node-entry.js:19563:40
04:29:59.990 | at async Promise.all (index 0)
04:29:59.990 | at async PluginDriver.hookParallel (file:///vercel/path0/node_modules/.pnpm/[email protected]/node_modules/rollup/dist/es/shared/node-entry.js:19491:9)
04:29:59.990 | at async Bundle.generate (file:///vercel/path0/node_modules/.pnpm/[email protected]/node_modules/rollup/dist/es/shared/node-entry.js:17921:13)
04:29:59.990 | at async file:///vercel/path0/node_modules/.pnpm/[email protected]/node_modules/rollup/dist/es/shared/node-entry.js:20479:27
04:29:59.990 | at async catchUnfinishedHookActions (file:///vercel/path0/node_modules/.pnpm/[email protected]/node_modules/rollup/dist/es/shared/node-entry.js:19907:16)
04:30:00.051 | Error: Command "npm run build" exited with 1

For the permission, I'm stilling checking. 🙏

@AloisSeckar
Copy link
Contributor Author

@Jinjiang why it runs an npm command, when the project is pnpm based? Can the build command be changed at Vercel? pnpm-lock.yaml should be up-to-date with vuejs/docs

@Jinjiang
Copy link
Member

Jinjiang commented May 7, 2024

Yes, it's npm run build. However, it just calls a npm script. I believe it's not related to this error.

I found the error was caused by this commit.
13f25c8

since the latest successful deployment is based on the previous one.

image

Do you think there is anything suspicious?

@AloisSeckar
Copy link
Contributor Author

No, but since I digged up what VitePress considers being a "dead link", I guess there must be some invalid relative link introduced with this. Probably on "Glossary" page. Or maybe somewhere else I point to .cs/NOTES.md. Thank you for investigating, I will check the code.

@AloisSeckar
Copy link
Contributor Author

Yay, got it - missed trailing slash 😞 - 0625778

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants