Error: Some functionality, such as asynchronous I/O, timeouts, and generating random values,...

"Error: Some functionality, such as asynchronous I/O, timeouts, and generating random values, can only be performed while handling a request.\n    at g.fetch (__next-on-pages-dist__/chunks/411.js:2:4658)\n    at k.fetch (__next-on-pages-dist__/chunks/411.js:7:14205)\n    at k.fetchJSON (__next-on-pages-dist__/chunks/411.js:7:14647)\n    at get locationUrl [as locationUrl] (__next-on-pages-dist__/chunks/411.js:7:17751)\n    at get locationUrl [as locationUrl] (__next-on-pages-dist__/chunks/411.js:7:15116)\n    at Et.getLogInUrl (__next-on-pages-dist__/chunks/411.js:7:11828)\n    at Et.authenticate (__next-on-pages-dist__/chunks/411.js:7:11080)\n    at b.logIn (__next-on-pages-dist__/chunks/411.js:7:16697)\n    at new Ur (__next-on-pages-dist__/chunks/568.js:348:52621)\n    at get instance [as instance] (__next-on-pages-dist__/chunks/568.js:348:52735)"

"Error: Some functionality, such as asynchronous I/O, timeouts, and generating random values, can only be performed while handling a request.\n    at g.fetch (__next-on-pages-dist__/chunks/411.js:2:4658)\n    at k.fetch (__next-on-pages-dist__/chunks/411.js:7:14205)\n    at k.fetchJSON (__next-on-pages-dist__/chunks/411.js:7:14647)\n    at get locationUrl [as locationUrl] (__next-on-pages-dist__/chunks/411.js:7:17751)\n    at get locationUrl [as locationUrl] (__next-on-pages-dist__/chunks/411.js:7:15116)\n    at Et.getLogInUrl (__next-on-pages-dist__/chunks/411.js:7:11828)\n    at Et.authenticate (__next-on-pages-dist__/chunks/411.js:7:11080)\n    at b.logIn (__next-on-pages-dist__/chunks/411.js:7:16697)\n    at new Ur (__next-on-pages-dist__/chunks/568.js:348:52621)\n    at get instance [as instance] (__next-on-pages-dist__/chunks/568.js:348:52735)"

Runs fine on local deployment with edge configurations, i'm not quite sure why i'm encountering this error with cloudflare pages.

SmultarOP•7/4/23, 10:09 PM

MY SAVIOR IS HERE

SSmultar MY SAVIOR IS HERE

James•7/4/23, 10:10 PM

Afraid not haha, I'm not sure what the cause might be

James•7/4/23, 10:10 PM

Please could you open an issue on the next-on-pages repository on GitHub for this issue. If possible, it would be very much appreciated if a reproduction could be provided along with it.

SmultarOP•7/4/23, 10:10 PM

cries

James•7/4/23, 10:12 PM

Just please try and provide as much information about your project as possible, or a reproduction

. It might be caused by a dependency doing something in the global scope, but hard to say without being able to dig in

SmultarOP•7/4/23, 10:12 PM

What confuses me if, its build and publishes.

JJames Just please try and provide as much information about your project as possible, ...

SmultarOP•7/4/23, 10:12 PM

I am doing stuff in the global scope

SmultarOP•7/4/23, 10:12 PM

import * as Realm from "realm-web";

const uri = process.env.DB_URI as string; // your mongodb connection string
const options = {};

declare global {
  var _mongoClientPromise: Promise<Realm.User>;
}

class Singleton {
  private static _instance: Singleton;
  private client: Realm.App;
  private clientPromise: Promise<Realm.User>;
  private constructor() {
    this.client = new Realm.App({ id: process.env.DB_APP_ID as string });
    this.clientPromise = this.client.logIn(Realm.Credentials.apiKey(process.env.DB_API_KEY as string));
    if (process.env.NODE_ENV === 'development') {
      // In development mode, use a global variable so that the value
      // is preserved across module reloads caused by HMR (Hot Module Replacement).
      global._mongoClientPromise = this.clientPromise;
    }
  }

  public static get instance() {
    if (!this._instance) {
      this._instance = new Singleton();
    }
    return this._instance.clientPromise;
  }
}
const clientPromise = Singleton.instance;

// Export a module-scoped MongoClient promise. By doing this in a
// separate module, the client can be shared across functions.
export default clientPromise;

import * as Realm from "realm-web";

const uri = process.env.DB_URI as string; // your mongodb connection string
const options = {};

declare global {
  var _mongoClientPromise: Promise<Realm.User>;
}

class Singleton {
  private static _instance: Singleton;
  private client: Realm.App;
  private clientPromise: Promise<Realm.User>;
  private constructor() {
    this.client = new Realm.App({ id: process.env.DB_APP_ID as string });
    this.clientPromise = this.client.logIn(Realm.Credentials.apiKey(process.env.DB_API_KEY as string));
    if (process.env.NODE_ENV === 'development') {
      // In development mode, use a global variable so that the value
      // is preserved across module reloads caused by HMR (Hot Module Replacement).
      global._mongoClientPromise = this.clientPromise;
    }
  }

  public static get instance() {
    if (!this._instance) {
      this._instance = new Singleton();
    }
    return this._instance.clientPromise;
  }
}
const clientPromise = Singleton.instance;

// Export a module-scoped MongoClient promise. By doing this in a
// separate module, the client can be shared across functions.
export default clientPromise;

James•7/4/23, 10:14 PM

Oh yep, that's it

SmultarOP•7/4/23, 10:14 PM

Soo I guess

SmultarOP•7/4/23, 10:14 PM

Don't do this at all?

James•7/4/23, 10:16 PM

Yeah, you should try and move it to happen at request-time instead

SmultarOP•7/4/23, 10:17 PM

I'll go ahead and try to figure out how to rewrite this without global scope...

SmultarOP•7/4/23, 10:17 PM

Im still new to typescript

SmultarOP•7/4/23, 10:17 PM

And this example was given to me

SmultarOP•7/4/23, 10:17 PM

But, hey were going somewhere!

James•7/4/23, 10:19 PM

Yeah, I mean, that would probably be useful to use in a next.js nodejs server, but it wouldn't be that helpful in a serverless environment. The idea behind writing the realm client like that is so it would only be instantiated once, which works well for lifelong nodejs servers, but in a serverless environment where everything exists for the duration of the request, well, the effect isn't really quite the same

SmultarOP•7/4/23, 10:20 PM

Sadly, I can't get mongodb to work in the edge runtime any other way @Better James

SmultarOP•7/4/23, 10:20 PM

To my currently level of knowledge

SmultarOP•7/4/23, 10:22 PM

Made the changes, heres to hoping :>

SmultarOP•7/4/23, 10:22 PM

Also happy 4th of july @Better James

SSmultar Also happy 4th of july @Better James

James•7/4/23, 10:22 PM

I'm British

SmultarOP•7/4/23, 10:23 PM

OH NO

SmultarOP•7/4/23, 10:23 PM

Im sorry!

SSmultar Sadly, I can't get mongodb to work in the edge runtime any other way @Better Jam...

James•7/4/23, 10:23 PM

Here's an old example that you might be able to take some inspiration from - https://github.com/mongodb-developer/cloudflare-worker-rest-api-atlas/blob/main/src/index.ts

JJames Yeah, you should try and move it to happen at request-time instead

SmultarOP•7/4/23, 10:31 PM

Same results.

SmultarOP•7/4/23, 10:31 PM

import * as Realm from "realm-web";

// Create a promise that resolves with the MongoClient.
type client = Realm.App;
type clientPromise = Promise<Realm.User>;

const Client: client = new Realm.App({ id: process.env.DB_APP_ID as string });
const ClientPromise: clientPromise = Client.logIn(Realm.Credentials.apiKey(process.env.DB_API_KEY as string));

export default ClientPromise;

import * as Realm from "realm-web";

// Create a promise that resolves with the MongoClient.
type client = Realm.App;
type clientPromise = Promise<Realm.User>;

const Client: client = new Realm.App({ id: process.env.DB_APP_ID as string });
const ClientPromise: clientPromise = Client.logIn(Realm.Credentials.apiKey(process.env.DB_API_KEY as string));

export default ClientPromise;

SmultarOP•7/4/23, 10:31 PM

This is all I did.

SmultarOP•7/4/23, 10:34 PM

Is there a way to run a fake cloudflare pages environment on my pc @Better James ?

SmultarOP•7/4/23, 10:35 PM

Some users have described this.

SmultarOP•7/4/23, 10:35 PM

But i'm unsure of where I would even begin to try messing arround with those options.

SSmultar ```ts import * as Realm from "realm-web"; // Create a promise that resolves wit...

James•7/5/23, 8:47 AM

That's basically the same as what you had before. In the example above, they're doing it at request time

SSmultar Is there a way to run a fake cloudflare pages environment on my pc @Better James...

James•7/5/23, 8:58 AM

oh and yeah,

npx wrangler pages dev .vercel/output/static --compatibility-flag=nodejs_compat

npx wrangler pages dev .vercel/output/static --compatibility-flag=nodejs_compat

JJames oh and yeah, `npx wrangler pages dev .vercel/output/static --compatibility-flag=...

SmultarOP•7/5/23, 10:16 AM

any other specific params?

SmultarOP•7/5/23, 10:16 AM

James•7/5/23, 10:27 AM

you have to build it with

npx @cloudflare/next-on-pages

npx @cloudflare/next-on-pages

first

SmultarOP•7/5/23, 10:29 AM

thx

SSmultar ```ts import * as Realm from "realm-web"; // Create a promise that resolves wit...

SmultarOP•7/5/23, 10:33 AM

Could help me understand why this doesn't work on run time? Is it because of the promise?

James•7/5/23, 10:35 AM

I believe so

SmultarOP•7/5/23, 10:36 AM

Is their a work arround for this kind of stuff?

SmultarOP•7/5/23, 10:36 AM

Cause, I would need to wait for the connection to succeed before doing anything else?

SmultarOP•7/5/23, 10:38 AM

When building, I have encountered another issue....

▲  Created all serverless functions in: 1.824s
▲  Error: Unable to find lambda for route: /search
▲  ERROR  Command failed with exit code 1: vercel build

▲  Created all serverless functions in: 1.824s
▲  Error: Unable to find lambda for route: /search
▲  ERROR  Command failed with exit code 1: vercel build

SmultarOP•7/5/23, 10:39 AM

@Better James

SmultarOP•7/5/23, 10:39 AM

/search

/search

is a static page

James•7/5/23, 10:44 AM

Are you using Windows?

James•7/5/23, 10:44 AM

I believe that's a bug with the Vercel CLI when using Windows. It stopped happening to me once I switched to Ubuntu via WSL