I would do the route as above, then create the AAAA Record

HHard@Work I would do the route as above, then create the AAAA Record

Y

yaniv.efraim•7/30/24, 8:29 AM

Not sure that I understand the dummy DNS record (sorry, new here....)
This one I understand:

routes = [
    { pattern = "*.wix-app.run/*", zone_name = "wix-app.run" }
]

routes = [
    { pattern = "*.wix-app.run/*", zone_name = "wix-app.run" }
]

routes = [
    { pattern = "*.wix-app.run/*", zone_name = "wix-app.run" }
]

routes = [
    { pattern = "*.wix-app.run/*", zone_name = "wix-app.run" }
]

Then manually create a DNS record (from the Dashbord)? Like this:

Yyaniv.efraim Not sure that I understand the dummy DNS record (sorry, new here....) This one I...

H

Hard@WorkOP•7/30/24, 8:31 AM

Yes, that is correct

HHard@Work Yes, that is correct

Y

yaniv.efraim•7/30/24, 8:32 AM

Thank you so much!
Is the AAAA dns with

the correct thing?

Yyaniv.efraim Thank you so much! Is the AAAA dns with `*` the correct thing?

H

Hard@WorkOP•7/30/24, 8:35 AM

That should be the ticket!

HHard@Work That should be the ticket!

Y

yaniv.efraim•7/30/24, 8:40 AM

I'm getting the following warning (not sure if this is because I'm using my test domain)..

HHard@Work That should be the ticket!

Y

yaniv.efraim•7/31/24, 9:41 AM

I just came across this on the docs site:

Yyaniv.efraim I just came across this on the docs site:

H

Hello, I’m Allie!•7/31/24, 11:45 AM

I think that is specifically for cases where you are adding a record for a single subdomain, rather than a wildcard

C

Chaika•7/31/24, 3:27 PM

yea that's not going to work for wildcards and in situations where you have an origin behind the worker, etc

C

Chaika•7/31/24, 3:28 PM

Custom Domains give you a free certificate, I think are more efficient by some margin because all routes need to be eval'd on each request, and custom domains are simpler, but both are an option for a reason

Y

yaniv.efraim•7/31/24, 3:28 PM

Hey,
I'm trying to use github action to deploy our worker, using

cloudflare/wrangler-action@v3

cloudflare/wrangler-action@v3

.
This is my yml file:

name: Deploy Worker
on:
  push:
    branches:
      - wrangler
jobs:
  deploy:
    runs-on: ubuntu-latest
    timeout-minutes: 60
    steps:
      - uses: actions/checkout@v4
      - name: Build & Deploy Worker
        uses: cloudflare/wrangler-action@v3
        with:
          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
          workingDirectory: "./cloudflare-services/platforms-dispatcher"

name: Deploy Worker
on:
  push:
    branches:
      - wrangler
jobs:
  deploy:
    runs-on: ubuntu-latest
    timeout-minutes: 60
    steps:
      - uses: actions/checkout@v4
      - name: Build & Deploy Worker
        uses: cloudflare/wrangler-action@v3
        with:
          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
          workingDirectory: "./cloudflare-services/platforms-dispatcher"

name: Deploy Worker
on:
  push:
    branches:
      - wrangler
jobs:
  deploy:
    runs-on: ubuntu-latest
    timeout-minutes: 60
    steps:
      - uses: actions/checkout@v4
      - name: Build & Deploy Worker
        uses: cloudflare/wrangler-action@v3
        with:
          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
          workingDirectory: "./cloudflare-services/platforms-dispatcher"

name: Deploy Worker
on:
  push:
    branches:
      - wrangler
jobs:
  deploy:
    runs-on: ubuntu-latest
    timeout-minutes: 60
    steps:
      - uses: actions/checkout@v4
      - name: Build & Deploy Worker
        uses: cloudflare/wrangler-action@v3
        with:
          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
          workingDirectory: "./cloudflare-services/platforms-dispatcher"

For some reason, it was trying to install a private npm package (from my main repo yarn.lock), failing over that:

Checking for existing Wrangler installation
  /usr/local/bin/npx --no-install wrangler --version
  npm error npx canceled due to missing packages and no YES option: ["wrangler@3.67.1"]
  
  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-07-31T13_20_24_246Z-debug-0.log
  ⚠️ Wrangler not found or version is incompatible. Installing...
📥 Installing Wrangler
  /usr/local/bin/npm i wrangler@3.13.2
  npm error code E404
  npm error 404 Not Found - GET https://registry.npmjs.org/@wix%2fambassador-bootstrap-plugin - Not found
  npm error 404
  npm error 404  '@wix/ambassador-bootstrap-plugin@^1.0.617' is not in this registry.
  npm error 404
  npm error 404 Note that you can also install from a
  npm error 404 tarball, folder, http url, or git url.
  
  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-07-31T13_20_31_572Z-debug-0.log

Checking for existing Wrangler installation
  /usr/local/bin/npx --no-install wrangler --version
  npm error npx canceled due to missing packages and no YES option: ["wrangler@3.67.1"]
  
  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-07-31T13_20_24_246Z-debug-0.log
  ⚠️ Wrangler not found or version is incompatible. Installing...
📥 Installing Wrangler
  /usr/local/bin/npm i wrangler@3.13.2
  npm error code E404
  npm error 404 Not Found - GET https://registry.npmjs.org/@wix%2fambassador-bootstrap-plugin - Not found
  npm error 404
  npm error 404  '@wix/ambassador-bootstrap-plugin@^1.0.617' is not in this registry.
  npm error 404
  npm error 404 Note that you can also install from a
  npm error 404 tarball, folder, http url, or git url.
  
  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-07-31T13_20_31_572Z-debug-0.log

Checking for existing Wrangler installation
  /usr/local/bin/npx --no-install wrangler --version
  npm error npx canceled due to missing packages and no YES option: ["wrangler@3.67.1"]
  
  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-07-31T13_20_24_246Z-debug-0.log
  ⚠️ Wrangler not found or version is incompatible. Installing...
📥 Installing Wrangler
  /usr/local/bin/npm i wrangler@3.13.2
  npm error code E404
  npm error 404 Not Found - GET https://registry.npmjs.org/@wix%2fambassador-bootstrap-plugin - Not found
  npm error 404
  npm error 404  '@wix/ambassador-bootstrap-plugin@^1.0.617' is not in this registry.
  npm error 404
  npm error 404 Note that you can also install from a
  npm error 404 tarball, folder, http url, or git url.
  
  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-07-31T13_20_31_572Z-debug-0.log

Checking for existing Wrangler installation
  /usr/local/bin/npx --no-install wrangler --version
  npm error npx canceled due to missing packages and no YES option: ["wrangler@3.67.1"]
  
  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-07-31T13_20_24_246Z-debug-0.log
  ⚠️ Wrangler not found or version is incompatible. Installing...
📥 Installing Wrangler
  /usr/local/bin/npm i wrangler@3.13.2
  npm error code E404
  npm error 404 Not Found - GET https://registry.npmjs.org/@wix%2fambassador-bootstrap-plugin - Not found
  npm error 404
  npm error 404  '@wix/ambassador-bootstrap-plugin@^1.0.617' is not in this registry.
  npm error 404
  npm error 404 Note that you can also install from a
  npm error 404 tarball, folder, http url, or git url.
  
  npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-07-31T13_20_31_572Z-debug-0.log

I tried having

packageManager: npm

packageManager: npm

packageManager: npm

packageManager: npm

but this causes the installation to get stuck:

npm error Exit handler never called!
  npm error This is an error with npm itself. Please report this error at:

npm error Exit handler never called!
  npm error This is an error with npm itself. Please report this error at:

npm error Exit handler never called!
  npm error This is an error with npm itself. Please report this error at:

npm error Exit handler never called!
  npm error This is an error with npm itself. Please report this error at:

Is there an option to pre-install Wrangler? What is the best practice here? What am I doing wrong?
Thanks!

J

J-Boogie•8/1/24, 2:02 AM

having trouble logging in via wrangler CLI in Github Codespaces. Is it not possible to run wrangler in Github Codespaces? I run 'npm wrangler login' and get a link and an error "[WARNING] Failed to open". The link will return back to a localhost error. Any help for this newb is appreciated.

JJ-Boogie having trouble logging in via wrangler CLI in Github Codespaces. Is it not possi...

J

J-Boogie•8/1/24, 2:52 AM

nevermind, got it working, had to add my Cloudflare Account ID and an API Token to Githubs 'Codespace user secretes'. works almost flawlessly now, just need to manually correct the port number in the generated url after running 'npm run dev'. hope this helps anyone running into the same issue. (source: https://developers.cloudflare.com/workers/wrangler/ci-cd/#api-token)

Cloudflare Docs

Run in CI/CD · Cloudflare Workers docs

Deploy your Workers within a CI/CD environment.

J

jltxwesley•8/1/24, 5:37 AM

Hello, how to specify routes with zone id in cli args? https://github.com/cloudflare/workers-sdk/issues/2086, couldn't find any examples in the doc.

GitHub

Issues · cloudflare/workers-sdk

Home to Wrangler, the CLI for Cloudflare Workers® - Issues · cloudflare/workers-sdk

Jjltxwesley Hello, how to specify routes with zone id in cli args? https://github.com/cloud...

H

Hello, I’m Allie!•8/1/24, 5:39 AM

Does it not work without it?

HHello, I’m Allie!Does it not work without it?

J

jltxwesley•8/1/24, 5:44 AM

In my case, I need to specify routes in cli args to override the default settings in toml config file.

Jjltxwesley In my case, I need to specify routes in cli args to override the default setting...

H

Hello, I’m Allie!•8/1/24, 5:52 AM

No, I mean does it not work if you just don’t provide a Zone ID, but just the route itself?

HHello, I’m Allie!No, I mean does it not work if you just **don’t** provide a Zone ID, but just th...

J

jltxwesley•8/1/24, 5:56 AM

It doesn't work, it gets invalid_script_name error, similar to this: https://community.cloudflare.com/t/pointing-subdomain-to-worker-route-question/98683

Jjltxwesley It doesn't work, it gets invalid_script_name error, similar to this: https://com...

H

Hello, I’m Allie!•8/1/24, 5:57 AM

What is the name of your Worker(directly from your

wrangler.toml

wrangler.toml

)?

HHello, I’m Allie!What is the name of your Worker(directly from your `wrangler.toml`)?

J

jltxwesley•8/1/24, 5:58 AM

Don't worry about, I figured out a different way to solve this.

H

hyperknot•8/2/24, 9:48 PM

Hi,

wrangler versions

wrangler versions

wrangler versions

wrangler versions is not working in 3.68, even though it's supposed to be there since a while.

J

jason•8/2/24, 11:06 PM

If this is the right place to leave Wrangler feedback, I found it aggravating that for the 3 methods below, you must specify names to them differently in order to end up with the same final resource name:

bunx wrangler d1 create mysite-staging
bunx wrangler r2 bucket create mysite-staging
bunx wrangler kv:namespace create staging

bunx wrangler d1 create mysite-staging
bunx wrangler r2 bucket create mysite-staging
bunx wrangler kv:namespace create staging

bunx wrangler d1 create mysite-staging
bunx wrangler r2 bucket create mysite-staging
bunx wrangler kv:namespace create staging

bunx wrangler d1 create mysite-staging
bunx wrangler r2 bucket create mysite-staging
bunx wrangler kv:namespace create staging

d1 and r2 behave consistently with each other and use the name provided: e.g.
```
mysite-staging
```
mysite-staging
```
mysite-staging
```
mysite-staging
kv is inconsistent with these and automatically preprends the name property from
```
wrangler.toml
```
```
wrangler.toml
```
, as
```
<nameFromWrangler>-<nameSpecified>
```
<nameFromWrangler>-<nameSpecified>
```
<nameFromWrangler>-<nameSpecified>
```
<nameFromWrangler>-<nameSpecified>
, or
```
worker-
```
worker-
```
worker-
```
worker-
if outside a dir containing
```
wrangler.toml
```
```
wrangler.toml
```
.

This inconsistency worsens the DX from what it could be.

For more consistency, kv could simply 1.) use the name provided, and 2.) throw an error if a resource with that name already exists--just as the other methods do.

J

jason•8/2/24, 11:06 PM

Unrelated: happy to see a

wrangler.json

wrangler.json

wrangler.json

wrangler.json coming!

A

Ashley•8/4/24, 11:24 AM

Is there a way to prevent

npm create cloudflare@2.21.1

npm create cloudflare@2.21.1

npm create cloudflare@2.21.1

npm create cloudflare@2.21.1 auto-upgrading to the latest minor version? I understand that, in a lot of cases, it's completely safe to use the latest minor as it's non-breaking.

However, if you're writing documentation or something more static than dev work, and want to reference the flow of this command, it effectively breaks that - and perhaps you're using X and it gets removed in future.

In my particular case, it's going to go into printed material, and I've been using

2.21.1

2.21.1

2.21.1

2.21.1 where the initial list of options is a long-ish list - now it's been tidied up to be into categories with the lists behind. This means anywhere this command is used needs rewriting to account for the new options - not a large amount of work - but if this happens again it then means the printed material would come across wrong, which would be fixed by pinning the version, but it refuses to run without upgrading to the latest minor.

A

Ashley•8/4/24, 11:35 AM

npm create cloudflare@2.21.1 -- --no-auto-update

npm create cloudflare@2.21.1 -- --no-auto-update

npm create cloudflare@2.21.1 -- --no-auto-update

npm create cloudflare@2.21.1 -- --no-auto-update (didn't realise this existed!)

S

snipeship•8/5/24, 1:31 AM

for some reason

wrangler deploy

wrangler deploy

wrangler deploy

wrangler deploy isn't working as it did before (on the same workspace):

✘ [ERROR] Missing entry-point: The entry-point should be specified via the command line (e.g. `wrangler deploy path/to/script`) or the `main` config field.

✘ [ERROR] Missing entry-point: The entry-point should be specified via the command line (e.g. `wrangler deploy path/to/script`) or the `main` config field.

✘ [ERROR] Missing entry-point: The entry-point should be specified via the command line (e.g. `wrangler deploy path/to/script`) or the `main` config field.

✘ [ERROR] Missing entry-point: The entry-point should be specified via the command line (e.g. `wrangler deploy path/to/script`) or the `main` config field.

K

kian•8/5/24, 1:39 AM

Are you sure you're in the right directory?

S

snipeship•8/5/24, 1:48 AM

fixed

S

snipeship•8/5/24, 1:48 AM

forgot it was

bun run deploy

bun run deploy

bun run deploy

bun run deploy

H

heloo_mrinal•8/5/24, 6:21 AM

anyone having a solution for this ?

V

Vero•8/5/24, 3:26 PM

Heyo. @Wrangler office hours will start August 5, 2024 https://discord.gg/cloudflaredev?event=1257618132206620702

S

Sébastien Morel•8/5/24, 6:16 PM

hello, here did someone got to work VSCode Debugger and Wrangler ?
I have searched in the diff channel and it seems 3-4 persons have the same issue (me included).
The first breakpoint is hit, but it's just loading, cannot skip etc.
any clue, hint to debug that?

!

!Eurossi•8/5/24, 9:29 PM

Hello, developers
I got error when I run the vite project on local.
The problem is this.

!

!Eurossi•8/5/24, 9:30 PM

Please help me. thanks

!

!Eurossi•8/5/24, 9:35 PM

wrangler 3.32.0 (update available 3.68.0)
-------------------------------------------------------
[wrangler:inf] Ready on http://127.0.0.1:8788
⎔ Starting local server...
Parsed 2 valid header rules.
[wrangler-UserWorker:wrn] The latest compatibility date supported by the installed Cloudflare Workers Runtime is "2
024-03-04",
but you've requested "2024-08-05". Falling back to "2024-03-04"...
Features enabled by your requested compatibility date may not be available.
Upgrade to

wrangler@3.68.0

wrangler@3.68.0

wrangler@3.68.0

wrangler@3.68.0 to remove this warning.
X [ERROR] service core:user:worker: Uncaught ReferenceError: process is not defined

at null.<anonymous> (dwdwibrtjo.js:182105:20) in
../node_modules/next/dist/client/has-base-path.js
at null.<anonymous> (dwdwibrtjo.js:28:51) in require22
at null.<anonymous> (dwdwibrtjo.js:182132:24) in
../node_modules/next/dist/shared/lib/router/utils/is-local-url.js
at null.<anonymous> (dwdwibrtjo.js:28:51) in require22
at null.<anonymous> (dwdwibrtjo.js:182861:23) in
../node_modules/next/dist/client/resolve-href.js
at null.<anonymous> (dwdwibrtjo.js:28:51) in require22
at null.<anonymous> (dwdwibrtjo.js:183532:24) in ../node_modules/next/dist/client/link.js
at null.<anonymous> (dwdwibrtjo.js:28:51) in require22
at null.<anonymous> (dwdwibrtjo.js:183916:23) in ../node_modules/next/link.js
at null.<anonymous> (dwdwibrtjo.js:28:51) in __require22

X [ERROR] MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional
logging output above.

B

Btc-TenW•8/6/24, 7:06 AM

I like wrangler

1

1.1.1.1APP•8/6/24, 6:29 PM

DNS over Discord: GitHub

View the DNS over Discord source code on GitHub at https://dns-over-discord.v4.wtf/github

M

mihaaai•8/6/24, 7:23 PM

Hey there!
I was wondering if this issue with Durable Objects from CF Pages within

wrangler dev

wrangler dev

has been acknowledged by anyone, or if someone is already on it: https://github.com/cloudflare/workers-sdk/issues/5918
I'm gonna need it in the near future and I'm trying to estimate the overall effort of my project if this feature gets implemented soon.

GitHub

🚀 Feature Request:RPC Support for Durable Objects in `wrangler dev`...

Describe the solution When binding a durable object using RPC that was defined in a different worker, it fails with: Cannot access

MyDurableObject#myMethod

MyDurableObject#myMethod

MyDurableObject#myMethod

MyDurableObject#myMethod as Durable Object RPC is not yet suppor...

Mmihaaai Hey there! I was wondering if this issue with **Durable Objects** from **CF Page...

C

Chinoman10•8/7/24, 1:06 PM

https://discord.com/channels/595317990191398933/920749372256419930/1261695579227164763

C

Chinoman10•8/7/24, 1:06 PM

Don't expect it anytime soon (this month, for example), as I haven't even heard rumours of it being a thing "soon".

C

Chinoman10•8/7/24, 1:08 PM

Also, considering the problem I'm having with not even being able to bind the DO (which I've already opened a ticket)... (see the last GH comment on that issue).

CChinoman10 Don't expect it anytime soon (this month, for example), as I haven't even heard ...

H

Hard@WorkOP•8/7/24, 1:10 PM

We are merging Pages into Workers soon, if that is what you mean?

HHard@Work We are merging Pages into Workers soon, if that is what you mean?

C

Chinoman10•8/7/24, 1:14 PM

Well that passed below the radar for me I guess. But that's super exciting news.

So I guess we'll have to reassess the current issues after that merge.

Is there an ETA (even if just a rough figure/ballpark)?

CChinoman10 Well that passed below the radar for me I guess. But that's super exciting news....

H

Hard@WorkOP•8/7/24, 1:17 PM

Around August 15th, according to: https://github.com/cloudflare/workers-sdk/pull/6325

GitHub

fix: Update copy for assets/legacy-assets flag and config key by Ca...

What this PR solves / how to test
This PR changes the copy for assets and legacy-assets flags & config keys from We are going to be changing its behavior on August 15th. to We are going to ...

C

Chinoman10•8/7/24, 1:24 PM

Yea I haven't even figured out what the 'assets' even are/represent, so...
I guess that isn't all that great news then.

CChinoman10 Yea I haven't even figured out what the 'assets' even are/represent, so... I gue...

H

Hard@WorkOP•8/7/24, 1:26 PM

Basically the

env.ASSETS

env.ASSETS

env.ASSETS

env.ASSETS binding in Functions, but for Workers(at least how I understand it)

C

Chinoman10•8/7/24, 1:27 PM

Ah, that's for grabbing static stuff from within the Workers/Functions, right? (like a static image that's on the front-end code, or a static JSON data file, for ex.)

That's cool I guess, but unfortunately for me it isn't the problem I'm having

I

Iggy•8/7/24, 7:55 PM

Why does

wrangler tail

wrangler tail

wrangler tail

wrangler tail typically take a long time to flush logs for a worker/DO?

Ooof2win2 hmm so it seems to be persistent when i already have the service running and i s...

O

outsideurimagination•8/8/24, 7:30 AM

Experienced the same. If I have worker A calling worker B, B needs to start before A. This makes it a bit complicated in a monorepo setup with a single dev command starting all workers as separate packages, but https://github.com/vercel/turbo/issues/1497#issuecomment-1424852247 gave me a workaround

GitHub

Support executing multiple dependent long-running tasks in parallel...

Describe the feature you'd like to request In our monorepo, we have multiple services that to some degree depend on each other. For local development, we have to start a mock service first, the...

CChinoman10 Ah, that's for grabbing static stuff from within the Workers/Functions, right? (...

W

Wallacy•8/8/24, 12:58 PM

That if i understand correctly will just make kv-assets-handler that is part of worker sites unnecessary. If each worker has 'assets' associated, then you can just use that like on CF-Pages (that already has the assets binding on functions). That means that features like Gradual deployments will just work. Today you cant use Gradual deployments with worker sites because KV is always pointing to the last version.

Its just a part of the 2023 merge for worker+pages: https://blog.cloudflare.com/pages-and-workers-are-converging-into-one-experience

The Cloudflare Blog

Bringing a unified developer experience to Cloudflare Workers and P...

Today we’re excited to announce that over the next year we will be working to bring together the best traits and attributes you know and love from each product into one powerful platform!

I would do the route as above, then create the AAAA Record

Similar Threads

Similar Threads

Similar Threads