Eusebio Trigo
Eusebio Trigo
Explore posts from servers
CDCloudflare DevelopersXXata
PostsComments
CDCloudflare Developers
Created by Eusebio Trigo on 4/24/2024 in #pages-help
Using next-international makes the app forget the language.
I have my app built and deployed to cloudflare. I have added internationalization using next-international. When I change the language in local, it is kept, and the text is changed accordingly, but when I push the code and it is deployed in Cloudflare, it does not happen anymore. I could post a video if required. Or access to the deployed environment deployed in CF Pages.
22 replies
CDCloudflare Developers
Created by Eusebio Trigo on 2/26/2024 in #workers-help
Execute some code before worker starts
Hi team, I would like to know if it is possible to execute something in a worker just once, at the start. Example: - subscribe to webhooks to a 3rd party system. - set up a "fetch" receiver or an app using Hono.
4 replies
CDCloudflare Developers
Created by Eusebio Trigo on 11/14/2023 in #pages-help
Error 1101 Worker threw exception
No description
12 replies
CDCloudflare Developers
Created by Eusebio Trigo on 11/5/2023 in #pages-help
Deployments failing using NextJS and next-on-pages
Hi, We have been deploying our nextjs application for quite some time, and we have been seeing several errors on building that we cannot really diagnose: one is: 
20:47:28.559    ▲  Detected Next.js version: 14.0.1
20:47:28.562    ▲  Running "yarn run build"
20:47:29.984    ▲  Attention: Next.js now collects completely anonymous telemetry regarding usage.
20:47:29.985    ▲  This information is used to shape Next.js' roadmap and prioritize features.
20:47:29.985    ▲  You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
20:47:29.985    ▲  https://nextjs.org/telemetry
20:47:30.112    ▲  ▲ Next.js 14.0.1
20:47:30.113    ▲  - Experiments (use at your own risk):
20:47:30.113    ▲    · webpackBuildWorker
20:47:30.113    ▲  
20:47:30.114    ▲  Creating an optimized production build ...
20:48:13.428    ▲  Error: Command "yarn run build" exited with 129
20:48:13.467    
20:48:13.467    ⚡️ The Vercel build (`npx vercel build`) command failed. For more details see the Vercel logs above.
20:48:13.467    ⚡️ If you need help solving the issue, refer to the Vercel or Next.js documentation or their repositories.
20:48:13.467    
20:48:13.502    Failed: Error while executing user command. Exited with error code: 1
20:48:13.511    Failed: build command exited with code: 1
20:48:15.475    Failed: error occurred while running build command
20:47:28.559    ▲  Detected Next.js version: 14.0.1
20:47:28.562    ▲  Running "yarn run build"
20:47:29.984    ▲  Attention: Next.js now collects completely anonymous telemetry regarding usage.
20:47:29.985    ▲  This information is used to shape Next.js' roadmap and prioritize features.
20:47:29.985    ▲  You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
20:47:29.985    ▲  https://nextjs.org/telemetry
20:47:30.112    ▲  ▲ Next.js 14.0.1
20:47:30.113    ▲  - Experiments (use at your own risk):
20:47:30.113    ▲    · webpackBuildWorker
20:47:30.113    ▲  
20:47:30.114    ▲  Creating an optimized production build ...
20:48:13.428    ▲  Error: Command "yarn run build" exited with 129
20:48:13.467    
20:48:13.467    ⚡️ The Vercel build (`npx vercel build`) command failed. For more details see the Vercel logs above.
20:48:13.467    ⚡️ If you need help solving the issue, refer to the Vercel or Next.js documentation or their repositories.
20:48:13.467    
20:48:13.502    Failed: Error while executing user command. Exited with error code: 1
20:48:13.511    Failed: build command exited with code: 1
20:48:15.475    Failed: error occurred while running build command
And other occurrences are out of heap memory limit (and we tried with the NODE_OPTIONS --max-old-space-size of 8192 (even when the console says it only accepts 7GB of mem). We can build in local, with no issues (yes, we have good hardware...). Is there a way to at least output some more information in the logs? Thanks, team!
88 replies
CDCloudflare Developers
Created by Eusebio Trigo on 11/5/2023 in #workers-help
Changes in the last XX hours
Hi team! I was checking our workers in the dashboard and some of them were displaying "Last modified 14 hours ago". We didn't deploy or changed any configuration. Is there a way to see what were those changes?
2 replies
CDCloudflare Developers
Created by Eusebio Trigo on 8/2/2023 in #pages-help
Error building pages Module build failed: UnhandledSchemeError: Reading from "node:crypto"
Hi team, I´m trying to move my NextJs app from Vercel to Pages and i´m getting several errors when building my application: Failed to compile. 12:58:58.301 ▲ node:crypto 12:58:58.302 ▲ Module build failed: UnhandledSchemeError: Reading from "node:crypto" is not handled by plugins (Unhandled scheme). 12:58:58.302 ▲ Webpack supports "data:" and "file:" URIs by default. 12:58:58.302 ▲ You may need an additional plugin to handle "node:" URIs. ... 12:58:58.304 ▲ node:fs/promises 12:58:58.305 ▲ Module build failed: UnhandledSchemeError: Reading from "node:fs/promises" is not handled by plugins (Unhandled scheme). 12:58:58.305 ▲ Webpack supports "data:" and "file:" URIs by default. 12:58:58.305 ▲ You may need an additional plugin to handle "node:" URIs. And several more. It seems it is related to using formidable (https://github.com/node-formidable/formidable). Is there anything I should change somewhere to make it work? I use formidable in some functions in the pages/api folder to read the form content. Thanks!
5 replies