Or is this vercel being dumb and in the build of nextjs not allowing an api to be used at all

UUnsmart Or is this vercel being dumb and in the build of nextjs not allowing an api to b...

K

kian•3/2/24, 2:55 AM

this

U

UnsmartOP•3/2/24, 2:56 AM

I see

K

kian•3/2/24, 2:56 AM

U

UnsmartOP•3/2/24, 3:14 AM

https://github.com/vercel/next.js/pull/36980

Found the PR where they added it lol

GitHub

feat(middleware): issues warnings when using node.js global APIs in...

What's in there?
Middleware, since they are ran on edge runtime, do not have access to Node.js globals. While #36434 addressed cases where a middleware would import a node.js module, this PR is...

U

UnsmartOP•3/2/24, 3:23 AM

lol trying to file an issue on the nextjs repo is way too much effort

L

luna•3/2/24, 4:16 AM

so that warning just needs to be disabled for next-on-pages, correct?

U

UnsmartOP•3/2/24, 4:19 AM

I dont think next-on-pages can modify that at all needs to be fixed on the actual nextjs repo

L

luna•3/2/24, 4:23 AM

no no i get that. what im asking is, this is supported when deployed correct? (if we get the error removed will it work?)

U

UnsmartOP•3/2/24, 4:23 AM

Oh I see, yes it would work when that is removed.

L

luna•3/2/24, 4:24 AM

in that case i wonder if i can get around this for now with patch-package.

Ffaye Hey, I published a version of nextjs on a cloudflare page using git integration...

F

faye•3/2/24, 2:30 PM

Could someone help me with this? Would be super greatful :x

F

faye•3/2/24, 2:37 PM

Running npm run build & npm run start works fine locally for me too

J

James•3/2/24, 2:46 PM

Can you try redeploying?

JJames Can you try redeploying?

F

faye•3/2/24, 2:46 PM

I did a lot of times, I changed a lot of the code, nothing helps

F

faye•3/2/24, 2:47 PM

They all succeed the build too, the real-time logs doesn't work (i get that error i previously posted, the image with the account not being found), i even created a new repo and made a new CF Page, still did not work

F

faye•3/2/24, 3:09 PM

Even worse: Using

npx wrangler pages dev -- npm run start

npx wrangler pages dev -- npm run start

npx wrangler pages dev -- npm run start

npx wrangler pages dev -- npm run start also works.. 1crying

F

faye•3/2/24, 3:53 PM

Update:
After making a new git repo and moving files one after one.. I figured something out.
Adding literally any page other than the main page shows a "Worker threw exception".. Literally anything, even a simple page using this:

export const runtime = 'edge';

export const metadata = {
  title: 'Forgot password?',
};

export default function Page() {
  return (
      <>
        <h1>Test</h1>
      </>
  );
}

export const runtime = 'edge';

export const metadata = {
  title: 'Forgot password?',
};

export default function Page() {
  return (
      <>
        <h1>Test</h1>
      </>
  );
}

export const runtime = 'edge';

export const metadata = {
  title: 'Forgot password?',
};

export default function Page() {
  return (
      <>
        <h1>Test</h1>
      </>
  );
}

export const runtime = 'edge';

export const metadata = {
  title: 'Forgot password?',
};

export default function Page() {
  return (
      <>
        <h1>Test</h1>
      </>
  );
}

I'm so annoyed about this, why is CF having so many issues with this project?

F

faye•3/2/24, 3:54 PM

https://github.com/Headpat-Community/web/tree/main/src/app/(main)

It's so empty :(
https://2f0267bb.headpat-web.pages.dev/

F

faye•3/2/24, 3:55 PM

removing the forgot-password folder will make it work again, is anyone able to help with this? I really need to continue :/

F

faye•3/2/24, 3:58 PM

From the real-time logs (that actually work now):

  "outcome": "exception",
  "scriptName": "pages-worker--2143245-production",
  "diagnosticsChannelEvents": [],
  "exceptions": [
    {
      "name": "Error",
      "message": "The script will never generate a response.",
      "timestamp": 1709395044277
    }
  ],
  "logs": [],
  "eventTimestamp": 1709395044224,

  "outcome": "exception",
  "scriptName": "pages-worker--2143245-production",
  "diagnosticsChannelEvents": [],
  "exceptions": [
    {
      "name": "Error",
      "message": "The script will never generate a response.",
      "timestamp": 1709395044277
    }
  ],
  "logs": [],
  "eventTimestamp": 1709395044224,

  "outcome": "exception",
  "scriptName": "pages-worker--2143245-production",
  "diagnosticsChannelEvents": [],
  "exceptions": [
    {
      "name": "Error",
      "message": "The script will never generate a response.",
      "timestamp": 1709395044277
    }
  ],
  "logs": [],
  "eventTimestamp": 1709395044224,

  "outcome": "exception",
  "scriptName": "pages-worker--2143245-production",
  "diagnosticsChannelEvents": [],
  "exceptions": [
    {
      "name": "Error",
      "message": "The script will never generate a response.",
      "timestamp": 1709395044277
    }
  ],
  "logs": [],
  "eventTimestamp": 1709395044224,

U

UnsmartOP•3/2/24, 3:58 PM

https://2f0267bb.headpat-web.pages.dev/(main)

https://2f0267bb.headpat-web.pages.dev/(main)

https://2f0267bb.headpat-web.pages.dev/(main)

https://2f0267bb.headpat-web.pages.dev/(main) this kinda works it does a 404 instead lol

F

faye•3/2/24, 3:58 PM

which makes no sense, it's a normal page: https://github.com/Headpat-Community/web/blob/main/src/app/(main)/page.jsx

F

faye•3/2/24, 4:00 PM

lol

F

faye•3/2/24, 4:12 PM

So I'm guessing this is a cloudflare issue and not on my side? Wouldn't for the life of me know where to look with literally no pages dead

U

UnsmartOP•3/2/24, 4:23 PM

I'd probably remove

(main)

(main)

(main)

(main) as the folder name and just make it main and see if it works. Might be because of the non url safe characters

J

James•3/2/24, 4:26 PM

it's a route group - a next.js feature for grouping routes with layouts in the app directory

Ffaye So I'm guessing this is a cloudflare issue and not on my side? Wouldn't for the ...

J

James•3/2/24, 4:26 PM

but yes, this is likely a cloudflare issue

JJames it's a route group - a next.js feature for grouping routes with layouts in the a...

F

faye•3/2/24, 4:30 PM

this, i also have other pages using the same exact things, there's close to no difference which the structure of the website

JJames but yes, this is likely a cloudflare issue

F

faye•3/2/24, 4:30 PM

What do I do?

F

faye•3/2/24, 4:31 PM

I emptied the repo even more, all the components (except a theme switcher) are gone, and only the main page + an additional page (which starts breaking) is in here:
https://github.com/Headpat-Community/web/tree/main/src

(https://f36105b2.headpat-web.pages.dev/ for the latest commit with.. nothing in it)

F

faye•3/2/24, 4:31 PM

lol

Ffaye I emptied the repo even more, all the components (except a theme switcher) are g...

J

James•3/2/24, 5:03 PM

running this one locally with wrangler is giving me an exception so looks like there might be a legit problem with this one

F

faye•3/2/24, 5:03 PM

but what? i have the same structure on other sites, same files, same everything

JJames running this one locally with wrangler is giving me an exception so looks like t...

F

faye•3/2/24, 5:04 PM

Could you remove the forgot-password folder and see if it works?

Ffaye Could you remove the forgot-password folder and see if it works?

J

James•3/2/24, 5:05 PM

downgrade to next@14.1.0

J

James•3/2/24, 5:05 PM

i downgraded and it worked

Original message was deleted

F

faye•3/2/24, 5:06 PM

i linked to the /main/src, sorry haha

JJames i downgraded and it worked

F

faye•3/2/24, 5:07 PM

When downgrading and using npm ci, it still says next.js 14.1.1, is there a specific command i need to run?

J

James•3/2/24, 5:09 PM

npm add next@14.1.0

F

faye•3/2/24, 5:09 PM

oh that works, thanks! let me push and see

JJames npm add next@14.1.0

F

faye•3/2/24, 5:14 PM

This seems to work on the test repo, will try on my main repo now

F

faye•3/2/24, 5:15 PM

You're a life saver!
Thanks James.

F

faye•3/2/24, 5:16 PM

Although I wonder why 1.4.1.1 is causing this many issues on CF? It's not like that much has changed

J

James•3/2/24, 5:18 PM

it looks like a bug they introduced in 14.0.2 and refuse to fix or accept my PR in nextjs to fix, but our regex hack for it isn't matching in your build

F

faye•3/2/24, 5:18 PM

ahh I see

F

faye•3/2/24, 5:18 PM

Well, thanks for the help!

J

James•3/2/24, 5:19 PM

no worries

Ffaye Although I wonder why 1.4.1.1 is causing this many issues on CF? It's not like t...

J

James•3/2/24, 5:28 PM

I think something about the minification they do has changed

J

James•3/2/24, 5:29 PM

There's a prerelease in this PR to fix it for 14.1.1

F

faye•3/2/24, 5:31 PM

Thanks!

Or is this vercel being dumb and in the build of nextjs not allowing an api to be used at all

Similar Threads

Similar Threads

Similar Threads