Cant deploy to vercel #123
Comments
|
Hey, @Joshswooft. You should instead report the error to Qwik. However, the message is quite clear: "/lib64/libm.so.6: version `GLIBC_2.29' not found". I don't know your operating system but I assume it is a Unix-like system. If so, you can try this: wget -4c https://ftp.gnu.org/gnu/glibc/glibc-2.29.tar.gz
tar -zxvf glibc-2.29.tar.gz
cd glibc-2.29
mkdir build_dir
cd build_dir
sudo ../configure --prefix=/opt/glibc
sudo make
sudo make install |
|
@siguici Thanks, I'll raise it with them. I'm using vercel so not sure how much control I have over what dependencies can be installed on their machines. |
|
I've re-opened this issue because whilst trying to make a minimum app that re-produced the issue the above GLIBC issue has disappeared but the qwikdev/astro error still remains. Here is the link to the source code Error: |
|
Can you specify how to reproduce this error? Because the build works perfectly on my side: > @0.0.1 build /home/siguici/fuzzy-waddle
> astro check && astro build
19:17:13 Types generated 249ms
19:17:13 [check] Getting diagnostics for Astro files in /home/siguici/fuzzy-waddle...
src/layouts/default.astro:16:17 - warning astro(4000): This script will be treated as if it has the `is:inline` directive because it contains an attribute. Therefore, features that require processing (e.g. using TypeScript or npm packages in the script) are unavailable.
See docs for more details: https://docs.astro.build/en/guides/client-side-scripts/#script-processing.
Add the `is:inline` directive explicitly to silence this hint.
16 <script async src="https://cdn.builder.io/js/qwik/qwikloader.js"
~~~~~
Result (8 files):
- 0 errors
- 0 warnings
- 1 hint
19:17:41 [@qwikdev/astro] astro:build:start
vite v5.2.12 building for production...
✓ 5 modules transformed.
dist/build/q-bundle-graph-le3z7r.json 0.06 kB │ gzip: 0.06 kB
dist/q-manifest.json 1.40 kB │ gzip: 0.58 kB
dist/qwik-prefetch-service-worker.js 3.58 kB
dist/build/q-DBB_4DJj.js 0.06 kB │ gzip: 0.07 kB
dist/build/q-Pc5tFKP5.js 0.34 kB │ gzip: 0.23 kB
dist/build/q-DRazCl8O.js 5.86 kB │ gzip: 2.93 kB
✓ built in 2.07s
19:17:43 [build] output: "server"
19:17:43 [build] directory: /home/siguici/fuzzy-waddle/.vercel/output/
19:17:43 [build] adapter: @astrojs/vercel/serverless
19:17:43 [build] Collecting build info...
19:17:43 [build] ✓ Completed in 2.81s.
19:17:43 [build] Building server entrypoints...
node_modules/.pnpm/@builder.io+sdk-qwik@0.14.21_@builder.io+qwik@1.5.5_undici@6.18.1_/node_modules/@builder.io/sdk-qwik/lib/node/node-evaluate-db446d2b.js (9:25): Use of eval in "node_modules/.pnpm/@builder.io+sdk-qwik@0.14.21_@builder.io+qwik@1.5.5_undici@6.18.1_/node_modules/@builder.io/sdk-qwik/lib/node/node-evaluate-db446d2b.js" is strongly discouraged as it poses security risks and may cause issues with minification.
19:18:01 [vite] ✓ built in 18.01s
19:18:01 [build] ✓ Completed in 18.07s.
prerendering static routes
19:18:02 ▶ src/pages/blog/[slug].astro
[Builder.io]: Error fetching data. Error: Missing API key
at generateContentUrl (file:///home/siguici/fuzzy-waddle/.vercel/output/_functions/chunks/prerender_bEkHZWr5.mjs:13466:24)
at fetchEntries (file:///home/siguici/fuzzy-waddle/.vercel/output/_functions/chunks/prerender_bEkHZWr5.mjs:13540:21)
at Module.getStaticPaths (file:///home/siguici/fuzzy-waddle/.vercel/output/_functions/chunks/prerender_bEkHZWr5.mjs:13562:32)
at callGetStaticPaths (file:///home/siguici/fuzzy-waddle/node_modules/.pnpm/astro@4.9.2_typescript@5.4.5/node_modules/astro/dist/core/render/route-cache.js:28:27)
at getPathsForRoute (file:///home/siguici/fuzzy-waddle/node_modules/.pnpm/astro@4.9.2_typescript@5.4.5/node_modules/astro/dist/core/build/generate.js:200:31)
at generatePage (file:///home/siguici/fuzzy-waddle/node_modules/.pnpm/astro@4.9.2_typescript@5.4.5/node_modules/astro/dist/core/build/generate.js:169:25)
at async generatePages (file:///home/siguici/fuzzy-waddle/node_modules/.pnpm/astro@4.9.2_typescript@5.4.5/node_modules/astro/dist/core/build/generate.js:113:11)
at async staticBuild (file:///home/siguici/fuzzy-waddle/node_modules/.pnpm/astro@4.9.2_typescript@5.4.5/node_modules/astro/dist/core/build/static-build.js:109:7)
at async AstroBuilder.build (file:///home/siguici/fuzzy-waddle/node_modules/.pnpm/astro@4.9.2_typescript@5.4.5/node_modules/astro/dist/core/build/index.js:133:5)
at async AstroBuilder.run (file:///home/siguici/fuzzy-waddle/node_modules/.pnpm/astro@4.9.2_typescript@5.4.5/node_modules/astro/dist/core/build/index.js:164:7)
19:18:02 ✓ Completed in 112ms.
19:18:02
finalizing server assets
19:18:02 [build] Rearranging server assets...
19:18:02 [@astrojs/vercel/serverless] Bundling function ../../_functions/entry.mjs
19:18:04 [build] Server built in 23.81s
19:18:04 [build] Complete! |
|
@siguici Hey, there are instructions in the README on that github link I posted which should help you get setup. I'm going to assume you didn't get that error because you didn't add your builderio public key nor create any blog content so therefore there is no content to be dynamically generated by Astro! Running: For more context I am running node version: |
|
I deployed it on Vercel successfully: Vercel CLI 34.2.3
? Set up and deploy “~/fuzzy-waddle”? yes
? Which scope do you want to deploy to? Sikessem
? Link to existing project? no
? What’s your project’s name? qwik-astro-fuzzy-waddle
? In which directory is your code located? ./
Local settings detected in vercel.json:
Auto-detected Project Settings (Astro):
- Build Command: astro build
- Development Command: astro dev --port $PORT
- Install Command: `yarn install`, `pnpm install`, `npm install`, or `bun install`
- Output Directory: dist
? Want to modify these settings? no
🔗 Linked to sikessem/qwik-astro-fuzzy-waddle (created .vercel)
🔍 Inspect: https://vercel.com/sikessem/qwik-astro-fuzzy-waddle/3UQRZ7cu5i1L2MGtG5P7TweUigKG [2s]
✅ Production: https://qwik-astro-fuzzy-waddle-d4adhpis5-sikessem.vercel.app [2s]
📝 Deployed to production. Run `vercel --prod` to overwrite later (https://vercel.link/2F).
💡 To change the domain or build command, go to https://vercel.com/sikessem/qwik-astro-fuzzy-waddle/settings |
|
@siguici Whats the url to the blog post? You definitely set that up as well? |
|
Hey, @Joshswooft. I would like you to try this method and let us know if you get any error with Qwik:
npm i -g vercel
cd /path/to/fuzzy-waddle
vercel |
|
Updated to version : Unfortunately I still get the same error logs :( I can try and make some more in-depth setup notes to try and re-produce the issue on your end. |
|
@siguici I've added a detailed README to the code: https://github.com/Joshswooft/fuzzy-waddle. Please make sure you have deleted the previous project and re-cloned it then follow the setup instructions. Hopefully this time you will see the bug |
|
Hi @Joshswooft. I followed the steps that you mentioned in https://github.com/Joshswooft/fuzzy-waddle on different environments including Node@18.17.0 (as you mentioned) and Node@20.14.0 as well as with NPM and PNPM and I actually encounter the same type of error. I hope @thejackshelton will take a look for further clarification. In the meantime, I'll take a closer look at the error on my end and see if I need to make a fix in the integration or report the error to Qwik. If you have any suggestions or other problems about this integration, please let us know. We will do the necessary. |
Error Message: QRLs can not be dynamically resolved, because it does not have a chunk path |
|
Hi @thejackshelton , @siguici Do you have any updates on this issue? |
|
Hey @thejackshelton and @siguici. Small update from me after spending a few hours tinkering around with stuff. If I amend the Then the error changes to: Now when I modify the The project will build successfully and the website will load however the blog content served from builder.io does not render. I feel like there is a rollup/vite option that needs to be specified here 🤔 The error above references a Which can be understood a little about here: |
Hey @Joshswooft! Thanks for your patience on this issue. This looks like a problem directly with the Builder.io CMS and Astro when using the Qwik SDK. I would bring this up on the builder.io forum. Happy to chime in as well on the post and see if there's anything they may need from us Qwik Astronauts 😄 A potential problem I could see is the builder SDK making an assumption of Qwik City being used, as that was previously the only meta framework used by Qwik. If there is an issue directly caused by this integration with a minimal reproduction also happy to debug, as @siguici mentioned above, Vercel appears to be working fine with the integration itself. |
|
@Joshswooft for the time being, I am going to close this issue. Let me know if a post is created on the builder.io forum (so we can figure out the builder sdk problem) and I can chime in. |
|
@thejackshelton Thanks for your reply and support for this issue. I ended up pivoting to web components for the time being as it's supported on builder.io. When I get the chance I will follow this up on their forum and post a link here (for anyone else interested) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I'm getting an error when I attempt to deploy an Astro + Qwik application to vercel.
npm dependencies:
Error logs:
The text was updated successfully, but these errors were encountered: