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

BefusOP•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

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

James•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

James•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
      },

     d1Databases: {
        MY_D1: undefined,
               ^ Required
      },

     d1Databases: {
        MY_D1: undefined,
               ^ Required
      },

J

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

looks like I had to do this instead to get it to work

setupDevBindings({
      'MY_D1': {
        type: 'd1',
        databaseName: 'MY_D1'
      }
    },
  });

setupDevBindings({
      'MY_D1': {
        type: 'd1',
        databaseName: 'MY_D1'
      }
    },
  });

setupDevBindings({
      'MY_D1': {
        type: 'd1',
        databaseName: 'MY_D1'
      }
    },
  });

setupDevBindings({
      'MY_D1': {
        type: 'd1',
        databaseName: 'MY_D1'
      }
    },
  });

JJoe looks like I had to do this instead to get it to work ```setupDevBindings({ ...

D

Donnager•1/10/24, 3:20 AM

super interesting that you removed

bindings

bindings

bindings

bindings and it works, possibly the API allows for both

J

James•1/10/24, 8:52 AM

Is that on the latest next-on-pages version?

JJames Is that on the latest next-on-pages version?

J

Joe•1/10/24, 2:27 PM

1.8.5

DDonnager super interesting that you removed `bindings` and it works, possibly the API all...

J

Joe•1/10/24, 2:37 PM

sorry I left out some key stuff, this works.

setupDevBindings({
    bindings: {
      'MY_D1': {
        type: 'd1',
        databaseName: 'locations-db'
      }
    },
  });

setupDevBindings({
    bindings: {
      'MY_D1': {
        type: 'd1',
        databaseName: 'locations-db'
      }
    },
  });

setupDevBindings({
    bindings: {
      'MY_D1': {
        type: 'd1',
        databaseName: 'locations-db'
      }
    },
  });

setupDevBindings({
    bindings: {
      'MY_D1': {
        type: 'd1',
        databaseName: 'locations-db'
      }
    },
  });

B

Bram•1/10/24, 11:14 PM

Is it possible to partly have local dev bindings and party remote dev bindings?

B

Bram•1/10/24, 11:15 PM

Let's say, I want to use D1 locally, but R2 remotely during local development

J

James•1/11/24, 8:29 AM

The next-dev submodule uses miniflare and does local bindings, so im afraid not

3

39dylan•1/11/24, 2:01 PM

New to using Next.js, I'm running

next build

next build

next build

next build for my static site and I'm seeing double the amount of files counting towards my limit for each webpage. Upon inspection there seems to be extra

.meta

.meta

.meta

.meta and

.rsc

.rsc

.rsc

.rsc files when building how can I disable non essential static site files like these? Also does Cloudflare Pages have an option for us to check what files are generated and distributed on their CDN after a build is finished?

J

James•1/11/24, 2:21 PM

rsc files are essential

JJames rsc files are essential

3

39dylan•1/11/24, 2:52 PM

Even for a static site? I don't mind missing out on prefetch. Would you recommend I go with something like Astro instead if this is the case?

3

39dylan•1/11/24, 3:09 PM

Upon closer inspection it seems

/out/

/out/

/out/

/out/ contains .txt files for each dynamic route page... not sure what these are but will investigate getting rid of them and my problem is fixed

DDeo Kumar I deployed it on Cloudflare pages https://themes.fineshopdesign.com/api/image?u...

D

Donnager•1/11/24, 5:36 PM

not sure if you are still around sir, but just wanted to say i started using this in dev and blown away how cool this is!

also curiously, how did you learn about the

path

path

setting in the config for the next image? the closest i see in the docs is

remote patterns

remote patterns

remote patterns

remote patterns and

loaders

loaders

loaders

loaders which seems the

path

path

route handler is just in a cleaner/concise syntax if i am understanding it correctly, but if that is wrong would be super interested to learn more!

339dylan Even for a static site? I don't mind missing out on prefetch. Would you recommen...

J

James•1/11/24, 5:52 PM

yes. the rsc file is needed for soft navigation. if nextjs cant get the rsc payload it needs, it will results in a hard refresh/navigation instead

DDonnager not sure if you are still around sir, but just wanted to say i started using thi...

D

Deo Kumar•1/11/24, 6:05 PM

Here is the documentation (legacy):
https://nextjs.org/docs/pages/api-reference/components/image-legacy#loader-configuration

Components: (Legacy) | Next.js

Backwards compatible Image Optimization with the Legacy Image component.

339dylan New to using Next.js, I'm running `next build` for my static site and I'm seeing...

D

Deo Kumar•1/11/24, 6:17 PM

To check the assets which were uploaded, you can navigate to deployment details > Assets Uploaded
Are you using output: "export" ?

DDeo Kumar To check the assets which were uploaded, you can navigate to deployment details ...

3

39dylan•1/11/24, 6:43 PM

Yes, I'm using static exports for next.js... tried the assets uploaded tab initially but my browser will crash when loading 18k files but it did give me info about

.txt

.txt

files being created for each page due to using App Router reverting to Pages Router fixes this.

3

39dylan•1/11/24, 6:47 PM

However it seems like i18n with Pages Router cannot

output: 'export'

output: 'export'

output: 'export'

output: 'export' so I'm back to square one

3

39dylan•1/11/24, 6:48 PM

I will try and modify my build script to delete

*.txt

*.txt

*.txt

*.txt files at the end and see how that goes

DDeo Kumar Here is the documentation (legacy): https://nextjs.org/docs/pages/api-reference/...

D

Donnager•1/11/24, 7:28 PM

okay interesting, yeah i don't see a reference to that approach, but thinking it through more i guess the idea is if you understand the primitives (html img element + api routes), it just naturally follows that the pattern works, i just need to learn more hehe

L

localλorse•1/11/24, 8:04 PM

Hey, is it possible to have a reverse proxy on cloudflare, so that I can merge a CF-hosted nextjs app with a hugo-generated static landing page and a hostinger-hosted blog, on different subdomains? (E.g. app on

app.mydomain.com

app.mydomain.com

app.mydomain.com

app.mydomain.com, blog on

blog.mydomain.com

blog.mydomain.com

blog.mydomain.com

blog.mydomain.com, landing page on

mydomain.com

mydomain.com

mydomain.com

mydomain.com)

B

BefusOP•1/12/24, 9:36 AM

I am trying to check if my request has been succesfull or errored but the return type is void, anyone know how to fix this?

BBefus I am trying to check if my request has been succesfull or errored but the return...

H

Hello, I’m Allie!•1/12/24, 9:40 AM

If that is a

KV

KV

KV

KV namespace, then it is valid behaviour that it returns void. It will throw an error if something goes wrong

B

BefusOP•1/12/24, 9:42 AM

Yea it's a KV namespace, I'm trying to show the use a message if something goes wrong is that not possible then?

BBefus Yea it's a KV namespace, I'm trying to show the use a message if something goes ...

H

Hello, I’m Allie!•1/12/24, 9:43 AM

You can use a

try/catch

try/catch

HHello, I’m Allie!You can use a `try/catch`

B

BefusOP•1/12/24, 12:10 PM

Thank you, this seems to work

T

t•1/12/24, 3:46 PM

Need help with Next on pages prod deployment. I get 500 Internal Server Error when loading the page. The preview deployment works fine for some reason, its just the production deployment

J

James•1/12/24, 4:05 PM

Are you using smart placement or log stream?

T

t•1/12/24, 4:26 PM

yes to smart placement, only look at real time logs occasionally for debugging, does that affect it?

J

James•1/12/24, 4:54 PM

disable smart placement and try redeploying

J

James•1/12/24, 4:55 PM

it's caused internal server errors when enabling it with pages for months now

T

t•1/12/24, 4:56 PM

just tried and seems to be working so far, thanks for the tip

T

t•1/12/24, 4:57 PM

any idea why it only happens on the production deployment?

J

James•1/12/24, 5:28 PM

because smart placement is broken with pages

A

advaith•1/16/24, 7:31 AM

trying to run it locally for development and getting this error

A

advaith•1/16/24, 7:32 AM

is it just the windows incompatibility?

J

James•1/16/24, 7:35 AM

Please can you open an issue in the GitHub for this

B

BefusOP•1/20/24, 11:25 AM

In production with this ssg generated page we get a ton of requests like this, anybody familiar with this?

B

BefusOP•1/20/24, 11:26 AM

I believe it has something to do with caching, just not sure

BBefus In production with this ssg generated page we get a ton of requests like this, a...

J

James•1/20/24, 12:02 PM

That looks like Next.js' default prefetching behaviour when using the Next.js Link component. You can pass prefetch={false} I think it is to disable this behaviour.

Can you show what errors exactly you are getting

Similar Threads

Similar Threads

Similar Threads