And when that won't work, who can we talk to? how do I even know if they are looking at my reports?
And when that won't work, who can we talk to? how do I even know if they are looking at my reports?
@aws-sdk/client-ses, it seems that aws-sdk (the lib i was using) is old and will be depricated next year. Everything works fine now fs)example.com is a Cloudflare Zone inside Account ID 1, and a Cloudflare Pages project exists for Account ID 2. example.com (the apex) be added as a Custom Domain on the Pages project? Or do you need to actually own the zone / have access to the zone for it to work?wrangler.toml to account for the fact that I have a Pages app, a production database, and a preview database. The prod and preview DBs are bound to their respective environments via dash app as "DB".wrangler pages dev with the preview_database_id set to my actual previews database id, am I running locally with my previews database remote from the edge?wrangler.toml to not have the actual preview_database_id and replace it with just "DB"?wrangler pages dev output about bindings in both scenarios and what these mean:wrangler.toml is correct because my CI migration wrangler d1 migrations apply with and without --preview appear to be running on the expected DBs. I'm just still quite a bit confused about how this should be set up for local dev. I could maybe use a separate .toml file for local dev? I could try to remember to change the file each time I want to work locally? Maybe I'm missing something?wrangler.toml. Is there experimental support for this already? Any docs or tips on how we can use this?npm create cloudflare@latest to create a new Next.js project. getRequestContext().env.DB... and to use getRequestContext I need the runtime to be edge. As soon as I add that runtime constant, all hell breaks loose and it complains about node:crypto etc whenever I do a build. What am I doing that's really dumb?oslo/password and trying to use Scrypt from it, and Lucia has its own one that is pure JS The hostname is part of a banned domain. This web property cannot be added to Cloudflare at this time. If you are an Enterprise customer, please contact your Customer Success Manager. Otherwise, please email abusereply@cloudflare.com with the name of the web property and a detailed explanation of your association with this web property.[[d1_databases]]
binding = "DB"
database_id = "014f4d7a-7d36-4c40-ada2-d0015f8a6471"
database_name = "my-db"
migrations_dir = "./functions/database/migrations"
preview_database_id = "406e7298-a837-4451-bec2-a6a229aac08d"
# preview_database_id = "DB"Your worker has access to the following bindings:
- D1 Databases:
- DB: my-db (406e7298-a837-4451-bec2-a6a229aac08d), Preview: (406e7298-a837-4451-bec2-a6a229aac08d)Module build failed: UnhandledSchemeError: Reading from "node:crypto" is not handled by plugins (Unhandled scheme).
Import trace for requested module:
▲ node:crypto
▲ ./node_modules/oslo/dist/password/scrypt.js
▲ ./node_modules/oslo/dist/password/index.js
▲ ./src/app/sign-up/page.tsx
▲
▲ ./src/app/sign-up/page.tsx + 30 modules
▲ Unexpected character '@' (1:37)
▲ | const __WEBPACK_NAMESPACE_OBJECT__ = @node-rs/argon2;
▲ while analyzing module external assign "@node-rs/argon2" for concatenation
▲
▲ > Build failed because of webpack errors