wrangler 3.72.3 → 3.74.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +5 -5
- package/templates/middleware/middleware-scheduled.ts +15 -1
- package/wrangler-dist/cli.d.ts +9 -3
- package/wrangler-dist/cli.js +47357 -47225
- package/templates/no-op-assets-worker.ts +0 -33
|
@@ -1,33 +0,0 @@
|
|
|
1
|
-
/**
|
|
2
|
-
* This Worker is used as a default entry-point for Assets-only
|
|
3
|
-
* Workers. It proxies the request directly on to the Asset Sever
|
|
4
|
-
* Worker service binding.
|
|
5
|
-
*
|
|
6
|
-
* In an Assets-only Workers world, we want to enable users
|
|
7
|
-
* to deploy a Worker with Assets without ever having to provide
|
|
8
|
-
* a User Worker.
|
|
9
|
-
*
|
|
10
|
-
* ```bash
|
|
11
|
-
* wrangler dev --experimental-assets dist
|
|
12
|
-
* wrangler deploy --experimental-assets dist
|
|
13
|
-
* ```
|
|
14
|
-
*
|
|
15
|
-
* ```toml
|
|
16
|
-
* name = "assets-only-worker"
|
|
17
|
-
* compatibility_date = "2024-01-01"
|
|
18
|
-
* ```
|
|
19
|
-
*
|
|
20
|
-
* Without a user-defined Worker, which usually serves as the entry
|
|
21
|
-
* point in the bundling process, wrangler needs to default to some
|
|
22
|
-
* other entry-point Worker for all intents and purposes. This is what
|
|
23
|
-
* this Worker is.
|
|
24
|
-
*/
|
|
25
|
-
type Env = {
|
|
26
|
-
ASSET_SERVER: Fetcher;
|
|
27
|
-
};
|
|
28
|
-
|
|
29
|
-
export default {
|
|
30
|
-
async fetch(request: Request, env: Env) {
|
|
31
|
-
return env.ASSET_SERVER.fetch(request);
|
|
32
|
-
},
|
|
33
|
-
};
|