is it in the yarn lock file and `node_modules` folder? the command is indeed saying that it can't fi

"use server";

import { getRequestContext } from "@cloudflare/next-on-pages";
import { Repository, getDB } from "@my-separate-package/db";

export const db = getDB(getRequestContext().env.DB ?? process.env.DB);

export const repository = new Repository(db);

"use server";

import { getRequestContext } from "@cloudflare/next-on-pages";
import { Repository, getDB } from "@my-separate-package/db";

export const db = getDB(getRequestContext().env.DB ?? process.env.DB);

export const repository = new Repository(db);

bun•3/9/24, 1:15 AM

but im getting

▲  Error: Failed to retrieve the Cloudflare request context.

▲  Error: Failed to retrieve the Cloudflare request context.

error when doing a

next build

next build

. it works fine in development

bun•3/9/24, 1:22 AM

ok.

process.env.NODE_ENV === "development"
    ? getRequestContext().env.DB
    : (process.env as any).DB

process.env.NODE_ENV === "development"
    ? getRequestContext().env.DB
    : (process.env as any).DB

works

Deo Kumar•3/9/24, 3:14 AM

I am using service bindings in my application, fetching assets in workers leads to 522 response code. Is there any way to fetch static assets from workers on same origins?

Bbun ok. `process.env.NODE_ENV === "development" ? getRequestContext().env.DB ...

DarioOP•3/9/24, 12:57 PM

@bun If you use the latest

beta

beta

release you can just use

process.env.DB

process.env.DB

both in development and production (

process.env

process.env

not working in development was a bug I've fixed here: https://github.com/cloudflare/next-on-pages/pull/690)

ideally devs should always use

getRequestContext()

getRequestContext()

and not

process.env

process.env

, but it seems like

getRequestContext()

getRequestContext()

has some bug that makes it not work in some cases, I'll definitely look into that the only thing is that I haven't gotten a minimal reproduction to play with that till now (I did briefly tried to reproduce it with no luck, I should also try that again if I can't get a minimal repro)

(PS: if you do have a reproduction that you can share please throw it my way!

)

DDeo Kumar I am using service bindings in my application, fetching assets in workers leads ...

DarioOP•3/9/24, 1:00 PM

can you share your code? how are you trying to fetch your assets? have you tried with

kv-asset-handler

kv-asset-handler

? (https://github.com/cloudflare/workers-sdk/tree/main/packages/kv-asset-handler)

Deo Kumar•3/9/24, 1:37 PM

I want to fetch the static assets in

public

public

folder.
Suppose my pages is deployed on

example.com

example.com

with a static file

favicon.ico

favicon.ico

.
I used service binding in the same app which tries to fetch

example.com/favicon.ico

example.com/favicon.ico

.

I need to fetch images files uploaded on pages after build for optimisation using wasm

Deo Kumar•3/9/24, 1:40 PM

The worker fetches files if routed to different origin but respond with 522 when same origin.

Deo Kumar•3/9/24, 1:47 PM

https://fineshop.app/api/image?url=https://fineshop.app/logos/logo-512x512.png&w=256&q=75

https://image.fineshopdesign.workers.dev/image?url=https://fineshop.app/logos/logo-512x512.png&w=256&q=75

First one using service bindings but same workers.

DDario <@1068666142610161725> If you use the latest `beta` release you can just use `pr...

bun•3/9/24, 6:29 PM

do you still need a reproduction ?

Bbun do you still need a reproduction ?

DarioOP•3/9/24, 6:45 PM

yes

Isaac McFadyen•3/9/24, 9:22 PM

What version of Wrangler are you using?

James•3/9/24, 9:23 PM

Not sure what you're referring to. The Next.js docs are pretty clear about how API routes are written. Your screenshot above looks like a Pages function, not a Next.js API route, and next-on-pages only supports Next.js, not the functions directory.

James•3/9/24, 9:30 PM

@cloudflare/next-on-pages

@cloudflare/next-on-pages

is for deploying full-stack Next.js apps to Cloudflare Pages. Therefore, you should be using native Next.js features. The functions directory will not work with next-on-pages because we have our own worker to handle your requests. If you want to use the functions directory, you won't be able to use next-on-pages

James•3/9/24, 9:35 PM

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

James•3/9/24, 9:42 PM

If you want to deploy a full-stack Next.js application, you should use Next.js' features

is it in the yarn lock file and `node_modules` folder? the command is indeed saying that it can't fi

Similar Threads

Similar Threads

Similar Threads