Regarding fetch request caching in next-on-pages, we store the response in the workers cache API (th

A

AA•1/4/24, 10:22 PM

oh, maybe this doesnt work..

A

Andrew Murphy•1/4/24, 10:22 PM

Yeah you can't use revalidate with next on pages

J

JamesOP•1/4/24, 10:23 PM

Ah I guess they might not forward a page level revalidate to fetch requests.

A

Andrew Murphy•1/4/24, 10:23 PM

ask me how i know - 3 days wasted on it

J

JamesOP•1/4/24, 10:23 PM

The fetch request revalidate option works though

A

AA•1/4/24, 10:23 PM

I'll need to figure out how to wire that in.. (I'm using a GQL wrapper lib over fetch)..

JJames Regarding fetch request caching in next-on-pages, we store the response in the w...

A

AA•1/4/24, 10:25 PM

is there an easy way for me to get at the workers cache? to flush it or similar?

A

AA•1/4/24, 10:25 PM

it seems.. hidden with CF pages..

A

AA•1/4/24, 10:26 PM

i seem to have some data surviving between builds..

AAA is there an easy way for me to get at the workers cache? to flush it or similar?

J

JamesOP•1/4/24, 10:27 PM

You can use revalidatePath / revalidateTag to trigger a revalidation for the fetch requests or all fetch requests under a route. That will be the on-demand revalidation section in the docs

A

AA•1/4/24, 10:28 PM

oh. but nothing in the cloudflare console i can use to peek or destroy

J

JamesOP•1/4/24, 10:30 PM

You could add an API endpoint that you call that triggers the revalidation and is authenticated with a secret. Maybe a way to set it up to be automatically called on a successful deploy. Not sure.

A

AA•1/4/24, 10:30 PM

ooh this might work better than the rebuild thing i'm doing..

J

JamesOP•1/4/24, 10:31 PM

I would also assume clearing your zones cache would clear the cache API but I may be wrong

J

JamesOP•1/4/24, 10:32 PM

My personal opinion would be to have your data fetched from the CMS and have the fetch request set to revalidate on an interval, then when the CMS makes a change, trigger a revalidate for that route. Ideally your CMS would let you do something like a webhook or http call on a publish to trigger an endpoint that can clear the relevant route.

J

JamesOP•1/4/24, 10:32 PM

But I don't know how things would specifically work with your cms

J

JamesOP•1/4/24, 10:33 PM

Or your use case with the cms

A

AA•1/4/24, 10:33 PM

yea i'll have to peek and see.. i wonder if this triggers a re-run of

generateStaticParams

generateStaticParams

generateStaticParams

generateStaticParams as well

J

JamesOP•1/4/24, 10:34 PM

Nah, that's just a build time thing

A

AA•1/4/24, 10:37 PM

so that's really just a way to create some pages buildtime?

A

AA•1/4/24, 10:37 PM

(this is the thing thats actually breaking on me currently) tho your ideas are pretty solid

J

JamesOP•1/4/24, 10:47 PM

Yes generateStaticParams is supposed to be used for SSGing routes at build time

A

AA•1/4/24, 11:01 PM

yea think thats what i was trying to use. but seems to be messing up lots.. your idea is better tho i think

A

AA•1/4/24, 11:04 PM

most of these pages will change less than yearly, so i figured compiling would be sufficient

!

!, Priyanshu•1/7/24, 3:27 AM

how do setup my next project so it will work on cloudflare.

!

!, Priyanshu•1/7/24, 3:28 AM

please explain step by step

U

Unsmart•1/7/24, 3:29 AM

?pings

F

Flare•1/7/24, 3:29 AM

Please do not ping community members for non-moderation reasons. Doing so will not solve your issue faster and will make people less likely to want to help you.

U

Unsmart•1/7/24, 3:29 AM

https://developers.cloudflare.com/pages/framework-guides/deploy-a-nextjs-site/

!

!, Priyanshu•1/7/24, 4:06 AM

is there something wrong in the dependency?

!

!, Priyanshu•1/7/24, 4:08 AM

{
  "name": "portfolio-v3",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "next start",
    "lint": "next lint"
  },
  "dependencies": {
    "autoprefixer": "10.4.14",
    "eslint": "8.39.0",
    "eslint-config-next": "13.3.1",
    "glob": "^10.2.1",
    "globby": "^13.1.4",
    "next": "13.3.1",
    "next-cloudinary": "^4.4.0",
    "next-sitemap": "^4.0.7",
    "next-themes": "^0.2.1",
    "postcss": "8.4.23",
    "react": "18.2.0",
    "react-dom": "18.2.0",
    "react-icons": "^4.8.0",
    "react-vertical-timeline-component": "^3.6.0",
    "tailwindcss": "3.3.1"
  },
  "devDependencies": {
    "@cloudflare/next-on-pages": "^1.8.3",
    "@next/env": "^13.3.0",
    "vercel": "^28.4.0"
  }
}

{
  "name": "portfolio-v3",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "next start",
    "lint": "next lint"
  },
  "dependencies": {
    "autoprefixer": "10.4.14",
    "eslint": "8.39.0",
    "eslint-config-next": "13.3.1",
    "glob": "^10.2.1",
    "globby": "^13.1.4",
    "next": "13.3.1",
    "next-cloudinary": "^4.4.0",
    "next-sitemap": "^4.0.7",
    "next-themes": "^0.2.1",
    "postcss": "8.4.23",
    "react": "18.2.0",
    "react-dom": "18.2.0",
    "react-icons": "^4.8.0",
    "react-vertical-timeline-component": "^3.6.0",
    "tailwindcss": "3.3.1"
  },
  "devDependencies": {
    "@cloudflare/next-on-pages": "^1.8.3",
    "@next/env": "^13.3.0",
    "vercel": "^28.4.0"
  }
}

{
  "name": "portfolio-v3",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "next start",
    "lint": "next lint"
  },
  "dependencies": {
    "autoprefixer": "10.4.14",
    "eslint": "8.39.0",
    "eslint-config-next": "13.3.1",
    "glob": "^10.2.1",
    "globby": "^13.1.4",
    "next": "13.3.1",
    "next-cloudinary": "^4.4.0",
    "next-sitemap": "^4.0.7",
    "next-themes": "^0.2.1",
    "postcss": "8.4.23",
    "react": "18.2.0",
    "react-dom": "18.2.0",
    "react-icons": "^4.8.0",
    "react-vertical-timeline-component": "^3.6.0",
    "tailwindcss": "3.3.1"
  },
  "devDependencies": {
    "@cloudflare/next-on-pages": "^1.8.3",
    "@next/env": "^13.3.0",
    "vercel": "^28.4.0"
  }
}

{
  "name": "portfolio-v3",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "next start",
    "lint": "next lint"
  },
  "dependencies": {
    "autoprefixer": "10.4.14",
    "eslint": "8.39.0",
    "eslint-config-next": "13.3.1",
    "glob": "^10.2.1",
    "globby": "^13.1.4",
    "next": "13.3.1",
    "next-cloudinary": "^4.4.0",
    "next-sitemap": "^4.0.7",
    "next-themes": "^0.2.1",
    "postcss": "8.4.23",
    "react": "18.2.0",
    "react-dom": "18.2.0",
    "react-icons": "^4.8.0",
    "react-vertical-timeline-component": "^3.6.0",
    "tailwindcss": "3.3.1"
  },
  "devDependencies": {
    "@cloudflare/next-on-pages": "^1.8.3",
    "@next/env": "^13.3.0",
    "vercel": "^28.4.0"
  }
}

JJames `_redirects` wouldn't work because the worker takes priority over the redirects ...

S

subscriptions•1/7/24, 9:50 AM

I got some time to test this today, if we add _routes.json file and exclude these static routes then _redirects works

0

0x99•1/7/24, 3:33 PM

hey anyone knows how to solve this problem
Node.JS Compatibility Error
no nodejs_compat compatibility flag set

00x99 hey anyone knows how to solve this problem Node.JS Compatibility Error no nodejs...

J

JamesOP•1/7/24, 3:36 PM

In your Pages project, go to Settings > Functions > Compatibility Flags.
Configure a nodejs_compat flag for both production and preview.

J

JamesOP•1/7/24, 3:37 PM

It does say this in the error page.

JJames In your Pages project, go to Settings > Functions > Compatibility Flags. Configu...

0

0x99•1/7/24, 3:47 PM

added nodejs_compat
still showing same error

J

JamesOP•1/7/24, 3:49 PM

Redeploy your project.

!

!, Priyanshu•1/7/24, 3:53 PM

I added necessary dependency to my next js project but still having errors with deployment on cloudflare, it's working well with GitHub pages

!

!, Priyanshu•1/7/24, 3:56 PM

If anyone can help personally then please reply i will send you the repo link

!!, Priyanshu If anyone can help personally then please reply i will send you the repo link

B

Befus•1/7/24, 5:35 PM

Can you show what errors exactly you are getting

BBefus Can you show what errors exactly you are getting

!

!, Priyanshu•1/8/24, 1:15 AM

Resolution step
06:44:47.082    ➤ YN0032: │ fsevents@npm:2.3.2: Implicit dependencies on node-gyp are discouraged
06:44:51.988    ➤ YN0002: │ profile@workspace:. doesn't provide @next/env (p6dac0), requested by next-sitemap
06:44:51.989    ➤ YN0002: │ react-vertical-timeline-component@npm:3.6.0 doesn't provide react (p5d41b), requested by react-intersection-observer
06:44:51.989    ➤ YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code
06:44:51.993    ➤ YN0000: └ Completed in 8s 10ms
06:44:52.034    ➤ YN0000: ┌ Post-resolution validation
06:44:52.034    ➤ YN0028: │ The lockfile would have been modified by this install, which is explicitly forbidden.
06:44:52.035    ➤ YN0000: └ Completed
06:44:52.035    ➤ YN0000: Failed with errors in 8s 54ms
06:44:52.100    Error: Exit with error code: 1
06:44:52.100        at ChildProcess.<anonymous> (/snapshot/dist/run-build.js)
06:44:52.101        at Object.onceWrapper (node:events:652:26)
06:44:52.101        at ChildProcess.emit (node:events:537:28)
06:44:52.101        at ChildProcess._handle.onexit (node:internal/child_process:291:12)
06:44:52.109    Failed: build command exited with code: 1
06:44:53.264    Failed: error occurred while running build command

Resolution step
06:44:47.082    ➤ YN0032: │ fsevents@npm:2.3.2: Implicit dependencies on node-gyp are discouraged
06:44:51.988    ➤ YN0002: │ profile@workspace:. doesn't provide @next/env (p6dac0), requested by next-sitemap
06:44:51.989    ➤ YN0002: │ react-vertical-timeline-component@npm:3.6.0 doesn't provide react (p5d41b), requested by react-intersection-observer
06:44:51.989    ➤ YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code
06:44:51.993    ➤ YN0000: └ Completed in 8s 10ms
06:44:52.034    ➤ YN0000: ┌ Post-resolution validation
06:44:52.034    ➤ YN0028: │ The lockfile would have been modified by this install, which is explicitly forbidden.
06:44:52.035    ➤ YN0000: └ Completed
06:44:52.035    ➤ YN0000: Failed with errors in 8s 54ms
06:44:52.100    Error: Exit with error code: 1
06:44:52.100        at ChildProcess.<anonymous> (/snapshot/dist/run-build.js)
06:44:52.101        at Object.onceWrapper (node:events:652:26)
06:44:52.101        at ChildProcess.emit (node:events:537:28)
06:44:52.101        at ChildProcess._handle.onexit (node:internal/child_process:291:12)
06:44:52.109    Failed: build command exited with code: 1
06:44:53.264    Failed: error occurred while running build command

Resolution step
06:44:47.082    ➤ YN0032: │ fsevents@npm:2.3.2: Implicit dependencies on node-gyp are discouraged
06:44:51.988    ➤ YN0002: │ profile@workspace:. doesn't provide @next/env (p6dac0), requested by next-sitemap
06:44:51.989    ➤ YN0002: │ react-vertical-timeline-component@npm:3.6.0 doesn't provide react (p5d41b), requested by react-intersection-observer
06:44:51.989    ➤ YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code
06:44:51.993    ➤ YN0000: └ Completed in 8s 10ms
06:44:52.034    ➤ YN0000: ┌ Post-resolution validation
06:44:52.034    ➤ YN0028: │ The lockfile would have been modified by this install, which is explicitly forbidden.
06:44:52.035    ➤ YN0000: └ Completed
06:44:52.035    ➤ YN0000: Failed with errors in 8s 54ms
06:44:52.100    Error: Exit with error code: 1
06:44:52.100        at ChildProcess.<anonymous> (/snapshot/dist/run-build.js)
06:44:52.101        at Object.onceWrapper (node:events:652:26)
06:44:52.101        at ChildProcess.emit (node:events:537:28)
06:44:52.101        at ChildProcess._handle.onexit (node:internal/child_process:291:12)
06:44:52.109    Failed: build command exited with code: 1
06:44:53.264    Failed: error occurred while running build command

Resolution step
06:44:47.082    ➤ YN0032: │ fsevents@npm:2.3.2: Implicit dependencies on node-gyp are discouraged
06:44:51.988    ➤ YN0002: │ profile@workspace:. doesn't provide @next/env (p6dac0), requested by next-sitemap
06:44:51.989    ➤ YN0002: │ react-vertical-timeline-component@npm:3.6.0 doesn't provide react (p5d41b), requested by react-intersection-observer
06:44:51.989    ➤ YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code
06:44:51.993    ➤ YN0000: └ Completed in 8s 10ms
06:44:52.034    ➤ YN0000: ┌ Post-resolution validation
06:44:52.034    ➤ YN0028: │ The lockfile would have been modified by this install, which is explicitly forbidden.
06:44:52.035    ➤ YN0000: └ Completed
06:44:52.035    ➤ YN0000: Failed with errors in 8s 54ms
06:44:52.100    Error: Exit with error code: 1
06:44:52.100        at ChildProcess.<anonymous> (/snapshot/dist/run-build.js)
06:44:52.101        at Object.onceWrapper (node:events:652:26)
06:44:52.101        at ChildProcess.emit (node:events:537:28)
06:44:52.101        at ChildProcess._handle.onexit (node:internal/child_process:291:12)
06:44:52.109    Failed: build command exited with code: 1
06:44:53.264    Failed: error occurred while running build command

!

!, Priyanshu•1/8/24, 1:49 AM

@Befus

!

!, Priyanshu•1/8/24, 1:49 AM

Can you please checkout my project?

!!, Priyanshu ``` Resolution step 06:44:47.082 ➤ YN0032: │ fsevents@npm:2.3.2: Implicit dep...

B

Befus•1/8/24, 9:05 AM

It shows pretty clearly the errors, just check them out one by one

BBefus It shows pretty clearly the errors, just check them out one by one

!

!, Priyanshu•1/8/24, 3:54 PM

I tried every way but still, I'll be very thankful if you can help me by visiting my repo

D

Donnager•1/9/24, 6:21 PM

n00b Q: updated

next-on-pages

next-on-pages

and getting this:

TypeError: Cannot convert undefined or null to object
    at Function.entries (<anonymous>)
    at instantiateMiniflare (/node_modules/.pnpm/@cloudflare+next-on-pages@1.8.5_vercel@32.7.2_wrangler@3.22.4/node_modules/@cloudflare/next-on-pages/dist/next-dev/index.cjs:5877:12)
    at setupDevBindings (/node_modules/.pnpm/@cloudflare+next-on-pages@1.8.5_vercel@32.7.2_wrangler@3.22.4/node_modules/@cloudflare/next-on-pages/dist/next-dev/index.cjs:5868:20)

TypeError: Cannot convert undefined or null to object
    at Function.entries (<anonymous>)
    at instantiateMiniflare (/node_modules/.pnpm/@cloudflare+next-on-pages@1.8.5_vercel@32.7.2_wrangler@3.22.4/node_modules/@cloudflare/next-on-pages/dist/next-dev/index.cjs:5877:12)
    at setupDevBindings (/node_modules/.pnpm/@cloudflare+next-on-pages@1.8.5_vercel@32.7.2_wrangler@3.22.4/node_modules/@cloudflare/next-on-pages/dist/next-dev/index.cjs:5868:20)

TypeError: Cannot convert undefined or null to object
    at Function.entries (<anonymous>)
    at instantiateMiniflare (/node_modules/.pnpm/@cloudflare+next-on-pages@1.8.5_vercel@32.7.2_wrangler@3.22.4/node_modules/@cloudflare/next-on-pages/dist/next-dev/index.cjs:5877:12)
    at setupDevBindings (/node_modules/.pnpm/@cloudflare+next-on-pages@1.8.5_vercel@32.7.2_wrangler@3.22.4/node_modules/@cloudflare/next-on-pages/dist/next-dev/index.cjs:5868:20)

TypeError: Cannot convert undefined or null to object
    at Function.entries (<anonymous>)
    at instantiateMiniflare (/node_modules/.pnpm/@cloudflare+next-on-pages@1.8.5_vercel@32.7.2_wrangler@3.22.4/node_modules/@cloudflare/next-on-pages/dist/next-dev/index.cjs:5877:12)
    at setupDevBindings (/node_modules/.pnpm/@cloudflare+next-on-pages@1.8.5_vercel@32.7.2_wrangler@3.22.4/node_modules/@cloudflare/next-on-pages/dist/next-dev/index.cjs:5868:20)

if i comment out this config portion dev server comes back:

if (process.env.NODE_ENV === "development") {
  const { setupDevBindings } = require("@cloudflare/next-on-pages/next-dev");

  setupDevBindings({
    r2Buckets: {
      CLOUDFLARE_BUCKET: "CLOUDFLARE_BUCKET",
    },
    kvNamespaces: {
      CLOUDFLARE_KV: "CLOUDFLARE_KV",
    },
    d1Databases: {
      CLOUDFLARE_D1: "CLOUDFLARE_D1",
    },
    MY_DO: {
      type: "durable-object",
      service: {
        name: "CLOUDFLARE_DO",
      },
      className: "Counter",
    },
  });
}

if (process.env.NODE_ENV === "development") {
  const { setupDevBindings } = require("@cloudflare/next-on-pages/next-dev");

  setupDevBindings({
    r2Buckets: {
      CLOUDFLARE_BUCKET: "CLOUDFLARE_BUCKET",
    },
    kvNamespaces: {
      CLOUDFLARE_KV: "CLOUDFLARE_KV",
    },
    d1Databases: {
      CLOUDFLARE_D1: "CLOUDFLARE_D1",
    },
    MY_DO: {
      type: "durable-object",
      service: {
        name: "CLOUDFLARE_DO",
      },
      className: "Counter",
    },
  });
}

if (process.env.NODE_ENV === "development") {
  const { setupDevBindings } = require("@cloudflare/next-on-pages/next-dev");

  setupDevBindings({
    r2Buckets: {
      CLOUDFLARE_BUCKET: "CLOUDFLARE_BUCKET",
    },
    kvNamespaces: {
      CLOUDFLARE_KV: "CLOUDFLARE_KV",
    },
    d1Databases: {
      CLOUDFLARE_D1: "CLOUDFLARE_D1",
    },
    MY_DO: {
      type: "durable-object",
      service: {
        name: "CLOUDFLARE_DO",
      },
      className: "Counter",
    },
  });
}

if (process.env.NODE_ENV === "development") {
  const { setupDevBindings } = require("@cloudflare/next-on-pages/next-dev");

  setupDevBindings({
    r2Buckets: {
      CLOUDFLARE_BUCKET: "CLOUDFLARE_BUCKET",
    },
    kvNamespaces: {
      CLOUDFLARE_KV: "CLOUDFLARE_KV",
    },
    d1Databases: {
      CLOUDFLARE_D1: "CLOUDFLARE_D1",
    },
    MY_DO: {
      type: "durable-object",
      service: {
        name: "CLOUDFLARE_DO",
      },
      className: "Counter",
    },
  });
}

super open to any suggestions or if there is doc don't hesitate to point it out!

DDonnager n00b Q: updated `next-on-pages` and getting this: ``` TypeError: Cannot convert ...

J

JamesOP•1/9/24, 6:30 PM

Please can you try using it in this format:

setupDevBindings({
  bindings: {
    'MY_KV': {
      type: 'kv',
      id: 'MY_KV'
    },
  },
});

setupDevBindings({
  bindings: {
    'MY_KV': {
      type: 'kv',
      id: 'MY_KV'
    },
  },
});

setupDevBindings({
  bindings: {
    'MY_KV': {
      type: 'kv',
      id: 'MY_KV'
    },
  },
});

setupDevBindings({
  bindings: {
    'MY_KV': {
      type: 'kv',
      id: 'MY_KV'
    },
  },
});

Please can you also open an issue on the next-on-pages GitHub repo as it looks like the docs might need updating about the correct syntax.

JJames Please can you try using it in this format: ```ts setupDevBindings({ bindings...

D

Donnager•1/9/24, 7:19 PM

ohhhhh got it, this is awesome and it totally works! thank you!

also posted an issue and i believe i pinged you correctly, if i got the issue formatting wrong, don't hesitate to let me know!

J

JamesOP•1/9/24, 7:52 PM

Perfect, glad to hear it worked!

J

Joe•1/10/24, 1:48 AM

I set up my D1database like this

setupDevBindings({
    bindings: {
    //   MY_KV: {
    //     type: "kv",
    //     id: "MY_KV",
    //   },
      MY_D1: {
        type: 'd1',
        id: 'MY_D1'
      }
    },
  });

setupDevBindings({
    bindings: {
    //   MY_KV: {
    //     type: "kv",
    //     id: "MY_KV",
    //   },
      MY_D1: {
        type: 'd1',
        id: 'MY_D1'
      }
    },
  });

setupDevBindings({
    bindings: {
    //   MY_KV: {
    //     type: "kv",
    //     id: "MY_KV",
    //   },
      MY_D1: {
        type: 'd1',
        id: 'MY_D1'
      }
    },
  });

setupDevBindings({
    bindings: {
    //   MY_KV: {
    //     type: "kv",
    //     id: "MY_KV",
    //   },
      MY_D1: {
        type: 'd1',
        id: 'MY_D1'
      }
    },
  });

and it's giving me an error

     d1Databases: {
        MY_D1: undefined,
               ^ Required
      },

     d1Databases: {
        MY_D1: undefined,
               ^ Required
      },

Regarding fetch request caching in next-on-pages, we store the response in the workers cache API (th

how do setup my next project so it will work on cloudflare.

Similar Threads

Similar Threads

how do setup my next project so it will work on cloudflare.

Similar Threads