Jay
Jay
CDCloudflare Developers
Created by Jay on 5/22/2024 in #pages-help
Reached heap limit
We started getting random build errors and here is the error that we are receiving during build process: We have a react app that is using vite for builds. What might be the issue? Also added --max-old-space-size=8192 cmd to build command but no luck.
<--- JS stacktrace --->
19:35:49.630
19:35:49.630 FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
19:35:49.630 ----- Native stack trace -----
19:35:49.630
19:35:49.650 1: 0xb82c28 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [node]
19:35:49.651 2: 0xeed540 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
19:35:49.652 3: 0xeed827 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*,
19:35:49.866 Failed: Error while executing user command. Exited with error code: 134
19:35:49.876 Failed: build command exited with code: 1
19:35:50.816 Failed: error occurred while running build command
<--- JS stacktrace --->
19:35:49.630
19:35:49.630 FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
19:35:49.630 ----- Native stack trace -----
19:35:49.630
19:35:49.650 1: 0xb82c28 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [node]
19:35:49.651 2: 0xeed540 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
19:35:49.652 3: 0xeed827 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*,
19:35:49.866 Failed: Error while executing user command. Exited with error code: 134
19:35:49.876 Failed: build command exited with code: 1
19:35:50.816 Failed: error occurred while running build command
1 replies
CDCloudflare Developers
Created by Jay on 3/13/2024 in #workers-help
Resizing images without source URL
Hello community. Currently we have a image resizer worker to avoid extraorbitant fees of webflow. This works perfectly but its creating another issue. Normally webflow stores images like this: https://global-assets.com/image.jpg We transform it to this: https://example.com/cdn-cgi/https://global-assets.com/image.jpg Because transformed image now contains double slashes our this confuses search engines and causes to drop our SEO page rank. Is there a way to serve the images after converting like this: https://example.com/cdn-cgi/image.jpg ? I changed the script but then I got the error that cloudflare worker cannot find the source.
1 replies
CDCloudflare Developers
Created by Jay on 3/12/2024 in #pages-help
Cloudflare pages not reporting back to Github
No description
1 replies
CDCloudflare Developers
Created by Jay on 11/28/2023 in #pages-help
Caching Related Issues
We are operating our web-application on cloudflare pages and recently started having lot of issues from our customers after each release of the new version of the app. Here is an example: Failed to fetch dynamically imported module: https://app.textcortex.com/assets/dashboard-a152fa43.js Is this kind of issues related to cloudflare's caching? Is there any kind of config that we need to be aware of regarding our build config? Thanks for the help!
1 replies
CDCloudflare Developers
Created by Jay on 9/26/2023 in #pages-help
✘ [ERROR] Error: Pages only supports files up to 26.2 MB in size
I am not sure if there is a workaround but currently our whole CI CD is stuck because of this. What is the recommended workaround for this?
2 replies
CDCloudflare Developers
Created by Jay on 4/6/2023 in #pages-help
Deploying to pages with github actions: Branch Settings
Hello all I have a question regarding deployment with github actions. I set the branch as branch: production but cloudflare pages is still deploying it as preview How can I get around this? Here is the current .yml file for the github actions
name: Build and Deploy to Cloudflare Pages on Release

on:
release:
types: [created]

jobs:
deploy:
runs-on: ubuntu-latest
permissions:
contents: read
deployments: write
steps:
# checkout staging branch and build using npm with node 16
# set process.env.CI = false to prevent build from failing
- name: Checkout
uses: actions/checkout@v2
with:
ref: staging
- name: Use Node.js 16
uses: actions/setup-node@v2
with:
node-version: 16
- name: Set CI to false
run: echo "CI=false" >> $GITHUB_ENV
- name: Install dependencies
run: yarn install
# npx browserslist@latest --update-db
- name: update browserslist
run: npx browserslist@latest --update-db
- name: Build
run: yarn build
- name: Publish to Cloudflare Pages
uses: cloudflare/pages-action@v1
with:
apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
accountId: ACCOUNT_ID
branch: production
projectName: cortex-web-app
directory: build
name: Build and Deploy to Cloudflare Pages on Release

on:
release:
types: [created]

jobs:
deploy:
runs-on: ubuntu-latest
permissions:
contents: read
deployments: write
steps:
# checkout staging branch and build using npm with node 16
# set process.env.CI = false to prevent build from failing
- name: Checkout
uses: actions/checkout@v2
with:
ref: staging
- name: Use Node.js 16
uses: actions/setup-node@v2
with:
node-version: 16
- name: Set CI to false
run: echo "CI=false" >> $GITHUB_ENV
- name: Install dependencies
run: yarn install
# npx browserslist@latest --update-db
- name: update browserslist
run: npx browserslist@latest --update-db
- name: Build
run: yarn build
- name: Publish to Cloudflare Pages
uses: cloudflare/pages-action@v1
with:
apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
accountId: ACCOUNT_ID
branch: production
projectName: cortex-web-app
directory: build
3 replies
CDCloudflare Developers
Created by Jay on 2/2/2023 in #pages-help
Binary download from https://nodejs.org/dist/v16.14.2/node-v16.14.2-linux-x64.tar.xz failed
Build is failing although I can confirm that this is not related to the source code. For some reason it cannot download therefore build fails.
4 replies