Cloudflare Developers•4y ago

If you're not already, I'd recommend using something like https://volta.sh/ to pin the node version

If you're not already, I'd recommend using something like https://volta.sh/ to pin the node version for that project

Volta - The Hassle-Free JavaScript Tool Manager

Volta: Start your engines.

MMrBBot If you're not already, I'd recommend using something like https://volta.sh/ to p...

Hello, I’m Allie!•8/17/22, 8:38 AM

I am using VoltaVolta, but I didn't know you could pin for specific projects. Thanks!

Ggotfredsen I tought I was suposed to be able to do import data from "./data.json"; in wrang...

DaniFoldi•8/18/22, 7:37 PM

https://www.typescriptlang.org/tsconfig#resolveJsonModule

TSConfig Reference - Docs on every TSConfig option

From allowJs to useDefineForClassFields the TSConfig reference includes information about all of the active compiler flags setting up a TypeScript project.

DaniFoldi•8/18/22, 7:37 PM

this might be what you're looking for

Salzian•8/19/22, 12:08 AM

How exactly do environments work? I can see in the dashboard some hints. On the overview page, all my workers have a small

production

production

tag underneath their name, and the listing also mentions 1 environment1 environment. I can also see some info when I click Manage serviceManage service in the workers' overview.

However, when I try to use environments in my

wrangler.toml

wrangler.toml

and then deploy them using --env--env, wrangler deploys separate services with the env name from the

wrangler.toml

wrangler.toml

as a suffix to the name. Kinda defeats the whole purpose of mentioning environments in the dashboard in the first place.

Bildschirmfoto_2022-08-19_um_02.08.03.png

SSalzian How exactly do environments work? I can see in the dashboard some hints. On the ...

TheSunSide•8/19/22, 12:10 AM

For workers, it's always in the name (so 1)

TheSunSide•8/19/22, 12:11 AM

Unless you change a name, then it could be 2?* (not sure)

TheSunSide•8/19/22, 12:11 AM

For pages and other products they have multiple without modifying configs

SSalzian How exactly do environments work? I can see in the dashboard some hints. On the ...

Cyb3r-Jak3•8/19/22, 12:12 AM

That

production

production

relates to Service Environments https://developers.cloudflare.com/workers/learning/using-services/#service-environments which has been temporarily disabled while they work on the feature

Salzian•8/19/22, 12:12 AM

oooh, i was wondering. "what else could be there than workers". kinda forgot about pages.

CCyb3r-Jak3 That `production` relates to Service Environments https://developers.cloudflare....

Salzian•8/19/22, 12:12 AM

so there is a chance we see this feature for workers in the future?

TheSunSide•8/19/22, 12:13 AM

If you're using an env, it'll do WORKERNAME-ENVNAME

TheSunSide•8/19/22, 12:13 AM

so there no way to "accumulate them" rn

SSalzian so there is a chance we see this feature for workers in the future?

Cyb3r-Jak3•8/19/22, 12:14 AM

Yes the feature will most likely come back

Salzian•8/19/22, 12:14 AM

Alright. It's not a hindrance, obviously, I was just confused by this feature not being available for workers. I thought I was doing something wrong in the TOML file. Thanks @thesunside @Cyb3r-Jok3

SSalzian Alright. It's not a hindrance, obviously, I was just confused by this feature no...

TheSunSide•8/19/22, 12:15 AM

Yeah, it makes writing worker names a bit awkward

TheSunSide•8/19/22, 12:15 AM

*for bindings

Salzian•8/19/22, 12:15 AM

Not using bindings just yet

I'm still experimenting with workers mostly.

TheSunSide•8/19/22, 12:16 AM

oh well if you do, type the result name as the worker name pain

Salzian•8/19/22, 12:17 AM

Good to know. Maybe with environments coming back in the future, you can auto-bind to the corresponding environment

WillTolmie•8/19/22, 12:37 PM

Anyone else struggling to get "wrangler dev" to work at the mo? Publish works fine, worker with graphql server runs nicely, but I get a 504 timeout on dev

jjjrmy•8/19/22, 12:43 PM

I'm following the docs exactly?

npx wrangler pages dev dist --r2=BUCKET

npx wrangler pages dev dist --r2=BUCKET

> wrangler pages dev ./dist --r2=THEMES


✘ [ERROR] Unknown argument: r2

> wrangler pages dev ./dist --r2=THEMES


✘ [ERROR] Unknown argument: r2

jjjrmy•8/19/22, 12:46 PM

wrangler 2.0.24 (update available 2.0.26)

jjjrmy•8/19/22, 12:46 PM

I just upgraded to .26 and it seems to work

jjjrmy•8/19/22, 1:19 PM

when running that command though, I'm still not able to access my R2 instance

jjjrmy•8/19/22, 1:19 PM

Token Permissions:

Scope (Access)
- account (read)
- user (read)
- workers (write)
- workers_kv (write)
- workers_routes (write)
- workers_scripts (write)
- workers_tail (read)
- pages (write)
- zone (read)
- offline_access

Scope (Access)
- account (read)
- user (read)
- workers (write)
- workers_kv (write)
- workers_routes (write)
- workers_scripts (write)
- workers_tail (read)
- pages (write)
- zone (read)
- offline_access

jjjrmy•8/19/22, 1:20 PM

do I need to re-auth to access R2?

Walshy•8/19/22, 1:22 PM

It's local dev not remote dev so it doesn't have access to your R2 bucket

jjjrmy•8/19/22, 1:22 PM

https://developers.cloudflare.com/pages/platform/functions#using-r2-buckets-locally

Functions (beta) · Cloudflare Pages docs

Documentation for Cloudflare Pages, the best way to deploy your static and JAMstack sites

jjjrmy•8/19/22, 1:22 PM

While developing locally, you can interact with an R2 bucket by adding --r2=<BINDING> to your run command. For example, if your bucket is bound to BUCKET, you can access this bucket in local dev by running npx wrangler pages dev dist --r2=BUCKET.

While developing locally, you can interact with an R2 bucket by adding --r2=<BINDING> to your run command. For example, if your bucket is bound to BUCKET, you can access this bucket in local dev by running npx wrangler pages dev dist --r2=BUCKET.

jjjrmy•8/19/22, 1:23 PM

so what do I do?

jjjrmy•8/19/22, 1:26 PM

so then I have to make a worker that makes the R2 accessible

jjjrmy•8/19/22, 1:26 PM

your way seems easiest

jjjrmy•8/19/22, 1:28 PM

but this is not the same case as KV?

jjjrmy•8/19/22, 1:28 PM

because my KV seems to be working fine

Tilon•8/19/22, 9:25 PM

Does „wrangler dev —local“ with service bindings work for anyone? In the console it says that the local worker is successfully connected to the live service binding, so it looks like it „should“ work. However when the worker tried to access the service, it throws „NAME_OF_SERVICE_BINDING is undefined“

TTilon Does „wrangler dev —local“ with service bindings work for anyone? In the console...

TheSunSide•8/19/22, 9:26 PM

Are you using experimental_services(old) instead of services ? Did you specify the Miniflare.mount?

TTheSunSide Are you using experimental_services(old) instead of services ? Did you specify t...

Tilon•8/19/22, 9:27 PM

I only use [[services]] in the wrangler.toml

TTilon I only use [[services]] in the wrangler.toml

TheSunSide•8/19/22, 9:28 PM

You need to define [miniflare.mounts] so your local env knows where to fetch those workers

TheSunSide•8/19/22, 9:28 PM

I'm using miniflare directly, but it should be similar

Tilon•8/19/22, 9:29 PM

Thx, I will try that

Tilon•8/19/22, 9:31 PM

Ignored: "miniflare":
Wrangler does not use configuration in the

miniflare

miniflare

section. Unless you are using Miniflare
directly you can remove this section.

Tilon•8/19/22, 9:32 PM

Too bad, looks like there is a difference between wrangler local and „pure“ miniflare

TheSunSide•8/19/22, 9:38 PM

▲ [WARNING] This worker is bound to live services: MAIL_FETCH (mail@local), LOGGER_SERVER (logger@local)

local worker: Error: ⎔ Service bindings are not yet supported in local mode.

TheSunSide•8/19/22, 9:38 PM

Might need to wait for wrangler to do it

TheSunSide•8/19/22, 9:38 PM

If you want true "local"

tacomilkshake•8/19/22, 9:42 PM

New Wrangler dev defaults to 0.0.0.0 so I added [dev] ip = '127.0.0.1' to wrangler.toml. wrangler dev doesn't use that config and remains at 0.0.0.0. Seems like a bug, ya?

Original message was deleted

tacomilkshake•8/19/22, 10:01 PM

https://github.com/cloudflare/wrangler2/issues/1714

If you're not already, I'd recommend using something like https://volta.sh/ to pin the node version

Similar Threads