Ok, so, I have created an issue for my pull request, and have updated the pull request to identify t

Ok, so, I have created an issue for my pull request, and have updated the pull request to identify the new issue that it fixes. https://github.com/cloudflare/workers-sdk/issues/3385

GitHub

🚀 Feature Request: Allow Wrangler deployments to opt-in to expirati...

Background The place where I work has been using Wrangler 1.x, and likes having the old assets not immediately being removed from the KV storage when a new deploy happens. Reason: users that alread...

PPeter Belbin Ok, so, I have created an issue for my pull request, and have updated the pull r...

Max (@rozenmd)•6/1/23, 3:45 PM

Thanks Peter, much appreciated.

Noil•6/1/23, 5:52 PM

When is the wrangler-action github actions getting a update to Wrangler 3.0.0?

NNoil When is the wrangler-action github actions getting a update to Wrangler 3.0.0?

James•6/1/23, 10:13 PM

I don't think there's a timeline, but you can follow https://github.com/cloudflare/wrangler-action/issues/107

AAlexander Any plans to support older macs as in 11.7?

James•6/1/23, 10:14 PM

Unfortunately OS support for

workerd

workerd

(what's used for

wrangler dev

wrangler dev

now in v3) is VERY limited. I know the team want to expand this, but I would recommend sticking with wrangler v2 for now if you want to run it on older operating systems - it should work fine.

James•6/1/23, 10:15 PM

Wrangler v3 was released a little hastily and seemingly without much testing, but hopefully we'll see this improve in the near future

JJames I don't think there's a timeline, but you can follow https://github.com/cloudfla...

Walshy•6/1/23, 10:21 PM

note @_noil you can add

wranglerVersion: 3

wranglerVersion: 3

to use 3.x today

AAlexander I understand that, I just wanted to now if it was planned or not, I subscribed, ...

James•6/1/23, 10:24 PM

Yep the issue was in response to noil

Issues like https://github.com/cloudflare/workerd/issues/46 and https://github.com/cloudflare/workerd/issues/174 and https://github.com/cloudflare/workers-sdk/issues/3262 and https://github.com/cloudflare/workers-sdk/issues/3301 are more relevant to your issue.

James•6/1/23, 10:24 PM

I believe it'll come, but I'd stick with v2 for now.

LeftSpace•6/2/23, 6:32 PM

is there any fix for this?

LeftSpace•6/2/23, 6:32 PM

https://github.com/cloudflare/workers-sdk/issues/3292
exact same

GitHub

🐛 BUG: Wrangler fails to reload Rust · Issue #3292 · cloudflare/wor...

Which Cloudflare product(s) does this pertain to? Workers/Other, Wrangler What version of Wrangler are you using? 3.0.0 What operating system are you using? Linux, Mac Describe the Bug I can boot t...

LeftSpace•6/2/23, 6:32 PM

wrangler 3.0.1

LLeftSpace https://github.com/cloudflare/workers-sdk/issues/3292 exact same

kian•6/2/23, 6:34 PM

LeftSpace•6/2/23, 6:35 PM

no solution yet

LeftSpace•6/2/23, 6:35 PM

fair

LeftSpace•6/2/23, 6:35 PM

kian•6/2/23, 6:36 PM

If you don't necessarily need functionality that's only in Wrangler 3 then I'd recommend downgrading to Wrangler 2, 3 is in a rough spot right now.

LeftSpace•6/2/23, 6:50 PM

just figured out my way

nodemon --watch src --exec npm run dev

nodemon --watch src --exec npm run dev

nodemon.json

{
    "watch": ["lib.rs", "src/"],
    "ext": "rs"
}

{
    "watch": ["lib.rs", "src/"],
    "ext": "rs"
}

package.json

{
    "name": "worker1",
    "version": "0.0.0",
    "private": true,
    "scripts": {
        "deploy": "wrangler deploy",
        "dev": "wrangler dev"
    },
    "dependencies": {
        "wrangler": "^3.0.1"
    }
}

{
    "name": "worker1",
    "version": "0.0.0",
    "private": true,
    "scripts": {
        "deploy": "wrangler deploy",
        "dev": "wrangler dev"
    },
    "dependencies": {
        "wrangler": "^3.0.1"
    }
}

it restarts the wrangler if detects a changed file.

lokiwind•6/2/23, 7:09 PM

Hello, I have a worker that I created with dashboard without using wrangler.
How can I run this worker with wrangler.
I mean: How can I edit an employee created with Dashboard::I want to edit this worker with wrangler

Llokiwind Hello, I have a worker that **I created with dashboard** **without using wrangle...

Adam•6/2/23, 7:25 PM

You can run

wrangler init --from-dash <WORKER NAME>

wrangler init --from-dash <WORKER NAME>

to pull it down locally and develop with Wrangler. https://developers.cloudflare.com/workers/wrangler/commands/#init

AAdam You can run `wrangler init --from-dash <WORKER NAME>` to pull it down locally an...

lokiwind•6/2/23, 7:28 PM

What it means:

Therefore, it is recommended that you continue using the CLI.

Therefore, it is recommended that you continue using the CLI.

Llokiwind What it means: `Therefore, it is recommended that you continue using the CLI.`

Adam•6/2/23, 7:33 PM

There are currently some differences between the way Wrangler builds and bundles Worker code and the way it's handled via the dashboard. For that reason, we recommend that users that start deploying via Wrangler continue doing that. Eventually, we'd like to get parity so that you can develop your Worker interchangeably with Wrangler or the dashboard, but that's a ways off.

AAdam There are currently some differences between the way Wrangler builds and bundles...

lokiwind•6/2/23, 7:35 PM

Thank you, I understand, it is healthier to edit in the field in which I created it

AAdam There are currently some differences between the way Wrangler builds and bundles...

Unsmart•6/2/23, 7:36 PM

Does this also mean potentially that you can have direct github integration with the quick edit in the future that would be really cool create a branch in quick edit it be running there for testing while coding then push that to the branch go to github open pr and merge

UUnsmart Does this also mean potentially that you can have direct github integration with...

Adam•6/2/23, 8:07 PM

Yes! That would be great.

kian•6/4/23, 12:45 AM

that was fixed 2 days ago in workerd so I'd expect it to be fixed in the next release

kian•6/4/23, 12:45 AM

as for how to workaround it right now, I'm not too sure

JacobMGEvans•6/4/23, 3:02 PM

The team will be back in full force starting tomorrow, appreciate the community as usual.

Some really cool stuff talked about this last week.

I also have the TurboRepo + Monorepo standardization PR which is getting wrapped up. This will enable a lot of other improvements, and even feature work!!

Thanks again everyone!