create-cloudflare 0.0.0-e11e1691 → 0.0.0-e144f63f

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.
Files changed (80) hide show
  1. package/dist/cli.js +20238 -19347
  2. package/dist/tsconfig.tsbuildinfo +1 -0
  3. package/package.json +11 -9
  4. package/templates/analog/c3.ts +134 -0
  5. package/templates/analog/snippets/devBindingsModule.ts +7 -0
  6. package/templates/analog/templates/env.d.ts +13 -0
  7. package/templates/analog/templates/src/dev-bindings.ts +18 -0
  8. package/templates/analog/templates/worker-configuration.d.ts +4 -0
  9. package/templates/analog/templates/wrangler.toml +85 -0
  10. package/templates/angular/c3.ts +2 -2
  11. package/templates/astro/c3.ts +8 -8
  12. package/templates/astro/snippets/runtimeDeclaration.ts +2 -1
  13. package/templates/astro/templates/wrangler.toml +35 -2
  14. package/templates/common/js/wrangler.toml +11 -1
  15. package/templates/common/ts/package.json +2 -1
  16. package/templates/common/ts/src/index.ts +3 -0
  17. package/templates/common/ts/worker-configuration.d.ts +2 -14
  18. package/templates/common/ts/wrangler.toml +11 -1
  19. package/templates/hello-world/js/package.json +2 -1
  20. package/templates/hello-world/js/test/index.spec.js +17 -17
  21. package/templates/hello-world/js/vitest.config.js +8 -8
  22. package/templates/hello-world/js/wrangler.toml +11 -1
  23. package/templates/hello-world/ts/package.json +2 -1
  24. package/templates/hello-world/ts/src/index.ts +3 -17
  25. package/templates/hello-world/ts/test/index.spec.ts +17 -17
  26. package/templates/hello-world/ts/test/tsconfig.json +6 -9
  27. package/templates/hello-world/ts/vitest.config.ts +8 -8
  28. package/templates/hello-world/ts/worker-configuration.d.ts +4 -0
  29. package/templates/hello-world/ts/wrangler.toml +11 -1
  30. package/templates/hello-world-durable-object/c3.ts +1 -1
  31. package/templates/hello-world-durable-object/js/src/index.js +18 -14
  32. package/templates/hello-world-durable-object/js/wrangler.toml +12 -2
  33. package/templates/hello-world-durable-object/ts/package.json +2 -2
  34. package/templates/hello-world-durable-object/ts/src/index.ts +24 -16
  35. package/templates/hello-world-durable-object/ts/worker-configuration.d.ts +6 -0
  36. package/templates/hello-world-durable-object/ts/wrangler.toml +13 -4
  37. package/templates/hello-world-python/c3.ts +9 -0
  38. package/templates/hello-world-python/py/__dot__gitignore +68 -0
  39. package/templates/hello-world-python/py/package.json +13 -0
  40. package/templates/hello-world-python/py/src/entry.py +4 -0
  41. package/templates/hello-world-python/py/wrangler.toml +108 -0
  42. package/templates/hono/c3.ts +53 -0
  43. package/templates/hono/snippets/appDeclaration.ts +1 -0
  44. package/templates/hono/snippets/bindingsType.ts +3 -0
  45. package/templates/hono/templates/worker-configuration.d.ts +4 -0
  46. package/templates/hono/templates/wrangler.toml +107 -0
  47. package/templates/next/README.md +5 -5
  48. package/templates/next/c3.ts +11 -9
  49. package/templates/next/wrangler.toml +33 -1
  50. package/templates/nuxt/c3.ts +7 -7
  51. package/templates/nuxt/templates/worker-configuration.d.ts +1 -1
  52. package/templates/nuxt/templates/wrangler.toml +35 -2
  53. package/templates/openapi/ts/package.json +2 -1
  54. package/templates/openapi/ts/worker-configuration.d.ts +4 -0
  55. package/templates/openapi/ts/wrangler.toml +104 -0
  56. package/templates/pre-existing/c3.ts +5 -5
  57. package/templates/pre-existing/js/wrangler.toml +1 -0
  58. package/templates/queues/js/wrangler.toml +11 -1
  59. package/templates/queues/ts/package.json +2 -1
  60. package/templates/queues/ts/src/index.ts +3 -5
  61. package/templates/queues/ts/worker-configuration.d.ts +5 -0
  62. package/templates/queues/ts/wrangler.toml +11 -1
  63. package/templates/qwik/c3.ts +6 -6
  64. package/templates/qwik/templates/worker-configuration.d.ts +1 -1
  65. package/templates/qwik/templates/wrangler.toml +35 -2
  66. package/templates/remix/c3.ts +3 -3
  67. package/templates/remix/templates/worker-configuration.d.ts +1 -1
  68. package/templates/remix/templates/wrangler.toml +35 -2
  69. package/templates/scheduled/js/package.json +2 -2
  70. package/templates/scheduled/js/src/index.js +8 -1
  71. package/templates/scheduled/js/wrangler.toml +12 -2
  72. package/templates/scheduled/ts/package.json +3 -2
  73. package/templates/scheduled/ts/src/index.ts +4 -21
  74. package/templates/scheduled/ts/worker-configuration.d.ts +4 -0
  75. package/templates/scheduled/ts/wrangler.toml +12 -2
  76. package/templates/solid/c3.ts +9 -7
  77. package/templates/solid/templates/wrangler.toml +84 -0
  78. package/templates/svelte/c3.ts +9 -9
  79. package/templates/svelte/js/wrangler.toml +35 -2
  80. package/templates/svelte/ts/wrangler.toml +35 -2
@@ -1,3 +1,107 @@
1
+ #:schema node_modules/wrangler/config-schema.json
1
2
  name = "<TBD>"
2
3
  main = "src/index.ts"
3
4
  compatibility_date = "<TBD>"
5
+
6
+ # Automatically place your workloads in an optimal location to minimize latency.
7
+ # If you are running back-end logic in a Worker, running it closer to your back-end infrastructure
8
+ # rather than the end user may result in better performance.
9
+ # Docs: https://developers.cloudflare.com/workers/configuration/smart-placement/#smart-placement
10
+ # [placement]
11
+ # mode = "smart"
12
+
13
+ # Variable bindings. These are arbitrary, plaintext strings (similar to environment variables)
14
+ # Docs:
15
+ # - https://developers.cloudflare.com/workers/wrangler/configuration/#environment-variables
16
+ # Note: Use secrets to store sensitive data.
17
+ # - https://developers.cloudflare.com/workers/configuration/secrets/
18
+ # [vars]
19
+ # MY_VARIABLE = "production_value"
20
+
21
+ # Bind the Workers AI model catalog. Run machine learning models, powered by serverless GPUs, on Cloudflare’s global network
22
+ # Docs: https://developers.cloudflare.com/workers/wrangler/configuration/#workers-ai
23
+ # [ai]
24
+ # binding = "AI"
25
+
26
+ # Bind an Analytics Engine dataset. Use Analytics Engine to write analytics within your Pages Function.
27
+ # Docs: https://developers.cloudflare.com/workers/wrangler/configuration/#analytics-engine-datasets
28
+ # [[analytics_engine_datasets]]
29
+ # binding = "MY_DATASET"
30
+
31
+ # Bind a headless browser instance running on Cloudflare's global network.
32
+ # Docs: https://developers.cloudflare.com/workers/wrangler/configuration/#browser-rendering
33
+ # [browser]
34
+ # binding = "MY_BROWSER"
35
+
36
+ # Bind a D1 database. D1 is Cloudflare’s native serverless SQL database.
37
+ # Docs: https://developers.cloudflare.com/workers/wrangler/configuration/#d1-databases
38
+ # [[d1_databases]]
39
+ # binding = "MY_DB"
40
+ # database_name = "my-database"
41
+ # database_id = "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
42
+
43
+ # Bind a dispatch namespace. Use Workers for Platforms to deploy serverless functions programmatically on behalf of your customers.
44
+ # Docs: https://developers.cloudflare.com/workers/wrangler/configuration/#dispatch-namespace-bindings-workers-for-platforms
45
+ # [[dispatch_namespaces]]
46
+ # binding = "MY_DISPATCHER"
47
+ # namespace = "my-namespace"
48
+
49
+ # Bind a Durable Object. Durable objects are a scale-to-zero compute primitive based on the actor model.
50
+ # Durable Objects can live for as long as needed. Use these when you need a long-running "server", such as in realtime apps.
51
+ # Docs: https://developers.cloudflare.com/workers/wrangler/configuration/#durable-objects
52
+ # [[durable_objects.bindings]]
53
+ # name = "MY_DURABLE_OBJECT"
54
+ # class_name = "MyDurableObject"
55
+
56
+ # Durable Object migrations.
57
+ # Docs: https://developers.cloudflare.com/workers/wrangler/configuration/#migrations
58
+ # [[migrations]]
59
+ # tag = "v1"
60
+ # new_classes = ["MyDurableObject"]
61
+
62
+ # Bind a Hyperdrive configuration. Use to accelerate access to your existing databases from Cloudflare Workers.
63
+ # Docs: https://developers.cloudflare.com/workers/wrangler/configuration/#hyperdrive
64
+ # [[hyperdrive]]
65
+ # binding = "MY_HYPERDRIVE"
66
+ # id = "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
67
+
68
+ # Bind a KV Namespace. Use KV as persistent storage for small key-value pairs.
69
+ # Docs: https://developers.cloudflare.com/workers/wrangler/configuration/#kv-namespaces
70
+ # [[kv_namespaces]]
71
+ # binding = "MY_KV_NAMESPACE"
72
+ # id = "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
73
+
74
+ # Bind an mTLS certificate. Use to present a client certificate when communicating with another service.
75
+ # Docs: https://developers.cloudflare.com/workers/wrangler/configuration/#mtls-certificates
76
+ # [[mtls_certificates]]
77
+ # binding = "MY_CERTIFICATE"
78
+ # certificate_id = "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
79
+
80
+ # Bind a Queue producer. Use this binding to schedule an arbitrary task that may be processed later by a Queue consumer.
81
+ # Docs: https://developers.cloudflare.com/workers/wrangler/configuration/#queues
82
+ # [[queues.producers]]
83
+ # binding = "MY_QUEUE"
84
+ # queue = "my-queue"
85
+
86
+ # Bind a Queue consumer. Queue Consumers can retrieve tasks scheduled by Producers to act on them.
87
+ # Docs: https://developers.cloudflare.com/workers/wrangler/configuration/#queues
88
+ # [[queues.consumers]]
89
+ # queue = "my-queue"
90
+
91
+ # Bind an R2 Bucket. Use R2 to store arbitrarily large blobs of data, such as files.
92
+ # Docs: https://developers.cloudflare.com/workers/wrangler/configuration/#r2-buckets
93
+ # [[r2_buckets]]
94
+ # binding = "MY_BUCKET"
95
+ # bucket_name = "my-bucket"
96
+
97
+ # Bind another Worker service. Use this binding to call another Worker without network overhead.
98
+ # Docs: https://developers.cloudflare.com/workers/wrangler/configuration/#service-bindings
99
+ # [[services]]
100
+ # binding = "MY_SERVICE"
101
+ # service = "my-service"
102
+
103
+ # Bind a Vectorize index. Use to store and query vector embeddings for semantic search, classification and other vector search use-cases.
104
+ # Docs: https://developers.cloudflare.com/workers/wrangler/configuration/#vectorize-indexes
105
+ # [[vectorize]]
106
+ # binding = "MY_INDEX"
107
+ # index_name = "my-index"
@@ -23,7 +23,7 @@ export async function copyExistingWorkerFiles(ctx: C3Context) {
23
23
  "Please specify the name of the existing worker in this account?",
24
24
  label: "worker",
25
25
  defaultValue: ctx.project.name,
26
- }
26
+ },
27
27
  );
28
28
  }
29
29
 
@@ -46,22 +46,22 @@ export async function copyExistingWorkerFiles(ctx: C3Context) {
46
46
  env: { CLOUDFLARE_ACCOUNT_ID: ctx.account?.id },
47
47
  startText: "Downloading existing worker files",
48
48
  doneText: `${brandColor("downloaded")} ${dim(
49
- `existing "${ctx.args.existingScript}" worker files`
49
+ `existing "${ctx.args.existingScript}" worker files`,
50
50
  )}`,
51
- }
51
+ },
52
52
  );
53
53
 
54
54
  // copy src/* files from the downloaded worker
55
55
  await cp(
56
56
  join(tempdir, ctx.args.existingScript, "src"),
57
57
  join(ctx.project.path, "src"),
58
- { recursive: true }
58
+ { recursive: true },
59
59
  );
60
60
 
61
61
  // copy wrangler.toml from the downloaded worker
62
62
  await cp(
63
63
  join(tempdir, ctx.args.existingScript, "wrangler.toml"),
64
- join(ctx.project.path, "wrangler.toml")
64
+ join(ctx.project.path, "wrangler.toml"),
65
65
  );
66
66
  }
67
67
 
@@ -1,3 +1,4 @@
1
+ #:schema node_modules/wrangler/config-schema.json
1
2
  name = "<TBD>"
2
3
  main = "src/index.js"
3
4
  compatibility_date = "<TBD>"
@@ -1,10 +1,20 @@
1
+ #:schema node_modules/wrangler/config-schema.json
1
2
  name = "<TBD>"
2
3
  main = "src/index.js"
3
4
  compatibility_date = "<TBD>"
4
5
 
6
+ # Automatically place your workloads in an optimal location to minimize latency.
7
+ # If you are running back-end logic in a Worker, running it closer to your back-end infrastructure
8
+ # rather than the end user may result in better performance.
9
+ # Docs: https://developers.cloudflare.com/workers/configuration/smart-placement/#smart-placement
10
+ # [placement]
11
+ # mode = "smart"
12
+
5
13
  # Variable bindings. These are arbitrary, plaintext strings (similar to environment variables)
14
+ # Docs:
15
+ # - https://developers.cloudflare.com/workers/wrangler/configuration/#environment-variables
6
16
  # Note: Use secrets to store sensitive data.
7
- # Docs: https://developers.cloudflare.com/workers/wrangler/configuration/#environment-variables
17
+ # - https://developers.cloudflare.com/workers/configuration/secrets/
8
18
  # [vars]
9
19
  # MY_VARIABLE = "production_value"
10
20
 
@@ -5,7 +5,8 @@
5
5
  "scripts": {
6
6
  "deploy": "wrangler deploy",
7
7
  "dev": "wrangler dev",
8
- "start": "wrangler dev"
8
+ "start": "wrangler dev",
9
+ "cf-typegen": "wrangler types"
9
10
  },
10
11
  "devDependencies": {
11
12
  "typescript": "^5.0.4",
@@ -8,14 +8,12 @@
8
8
  * - Open a browser tab at http://localhost:8787/ to see your worker in action
9
9
  * - Run `npm run deploy` to publish your worker
10
10
  *
11
+ * Bind resources to your worker in `wrangler.toml`. After adding bindings, a type definition for the
12
+ * `Env` object can be regenerated with `npm run cf-typegen`.
13
+ *
11
14
  * Learn more at https://developers.cloudflare.com/workers/
12
15
  */
13
16
 
14
- export interface Env {
15
- // Example binding to a Queue. Learn more at https://developers.cloudflare.com/queues/javascript-apis/
16
- MY_QUEUE: Queue;
17
- }
18
-
19
17
  export default {
20
18
  // Our fetch handler is invoked on a HTTP request: we can send a message to a queue
21
19
  // during (or after) a request.
@@ -0,0 +1,5 @@
1
+ // Generated by Wrangler
2
+ // After adding bindings to `wrangler.toml`, regenerate this interface via `npm run cf-typegen`
3
+ interface Env {
4
+ MY_QUEUE: Queue;
5
+ }
@@ -1,10 +1,20 @@
1
+ #:schema node_modules/wrangler/config-schema.json
1
2
  name = "<TBD>"
2
3
  main = "src/index.ts"
3
4
  compatibility_date = "<TBD>"
4
5
 
6
+ # Automatically place your workloads in an optimal location to minimize latency.
7
+ # If you are running back-end logic in a Worker, running it closer to your back-end infrastructure
8
+ # rather than the end user may result in better performance.
9
+ # Docs: https://developers.cloudflare.com/workers/configuration/smart-placement/#smart-placement
10
+ # [placement]
11
+ # mode = "smart"
12
+
5
13
  # Variable bindings. These are arbitrary, plaintext strings (similar to environment variables)
14
+ # Docs:
15
+ # - https://developers.cloudflare.com/workers/wrangler/configuration/#environment-variables
6
16
  # Note: Use secrets to store sensitive data.
7
- # Docs: https://developers.cloudflare.com/workers/wrangler/configuration/#environment-variables
17
+ # - https://developers.cloudflare.com/workers/configuration/secrets/
8
18
  # [vars]
9
19
  # MY_VARIABLE = "production_value"
10
20
 
@@ -43,7 +43,7 @@ const addBindingsProxy = (ctx: C3Context) => {
43
43
  // Insert the env declaration after the last import (but before the rest of the body)
44
44
  visitProgram: function (n) {
45
45
  const lastImportIndex = n.node.body.findLastIndex(
46
- (t) => t.type === "ImportDeclaration"
46
+ (t) => t.type === "ImportDeclaration",
47
47
  );
48
48
  const lastImport = n.get("body", lastImportIndex);
49
49
  lastImport.insertAfter(...snippets.getPlatformProxyTs);
@@ -109,8 +109,8 @@ const populateCloudflareEnv = () => {
109
109
  ].map(([varName, type]) =>
110
110
  b.tsPropertySignature(
111
111
  b.identifier(varName),
112
- b.tsTypeAnnotation(b.tsTypeReference(b.identifier(type)))
113
- )
112
+ b.tsTypeAnnotation(b.tsTypeReference(b.identifier(type))),
113
+ ),
114
114
  );
115
115
 
116
116
  n.node.body.body = newBody;
@@ -134,9 +134,9 @@ const config: TemplateConfig = {
134
134
  configure,
135
135
  transformPackageJson: async () => ({
136
136
  scripts: {
137
- deploy: `${npm} run build && wrangler pages deploy ./dist`,
138
- preview: `${npm} run build && wrangler pages dev ./dist`,
139
- "build-cf-types": `wrangler types`,
137
+ deploy: `${npm} run build && wrangler pages deploy`,
138
+ preview: `${npm} run build && wrangler pages dev`,
139
+ "cf-typegen": `wrangler types`,
140
140
  },
141
141
  }),
142
142
  devScript: "dev",
@@ -1,4 +1,4 @@
1
1
  // Generated by Wrangler
2
- // After adding bindings to `wrangler.toml`, regenerate this interface via `npm build-cf-types`
2
+ // After adding bindings to `wrangler.toml`, regenerate this interface via `npm run cf-typegen`
3
3
  interface Env {
4
4
  }
@@ -1,9 +1,20 @@
1
+ #:schema node_modules/wrangler/config-schema.json
1
2
  name = "<TBD>"
2
3
  compatibility_date = "<TBD>"
4
+ pages_build_output_dir = "./dist"
5
+
6
+ # Automatically place your workloads in an optimal location to minimize latency.
7
+ # If you are running back-end logic in a Pages Function, running it closer to your back-end infrastructure
8
+ # rather than the end user may result in better performance.
9
+ # Docs: https://developers.cloudflare.com/pages/functions/smart-placement/#smart-placement
10
+ # [placement]
11
+ # mode = "smart"
3
12
 
4
13
  # Variable bindings. These are arbitrary, plaintext strings (similar to environment variables)
14
+ # Docs:
15
+ # - https://developers.cloudflare.com/pages/functions/bindings/#environment-variables
5
16
  # Note: Use secrets to store sensitive data.
6
- # Docs: https://developers.cloudflare.com/pages/functions/bindings/#environment-variables
17
+ # - https://developers.cloudflare.com/pages/functions/bindings/#secrets
7
18
  # [vars]
8
19
  # MY_VARIABLE = "production_value"
9
20
 
@@ -49,4 +60,26 @@ compatibility_date = "<TBD>"
49
60
  # Docs: https://developers.cloudflare.com/pages/functions/bindings/#service-bindings
50
61
  # [[services]]
51
62
  # binding = "MY_SERVICE"
52
- # service = "my-service"
63
+ # service = "my-service"
64
+
65
+ # To use different bindings for preview and production environments, follow the examples below.
66
+ # When using environment-specific overrides for bindings, ALL bindings must be specified on a per-environment basis.
67
+ # Docs: https://developers.cloudflare.com/pages/functions/wrangler-configuration#environment-specific-overrides
68
+
69
+ ######## PREVIEW environment config ########
70
+
71
+ # [env.preview.vars]
72
+ # API_KEY = "xyz789"
73
+
74
+ # [[env.preview.kv_namespaces]]
75
+ # binding = "MY_KV_NAMESPACE"
76
+ # id = "<PREVIEW_NAMESPACE_ID>"
77
+
78
+ ######## PRODUCTION environment config ########
79
+
80
+ # [env.production.vars]
81
+ # API_KEY = "abc123"
82
+
83
+ # [[env.production.kv_namespaces]]
84
+ # binding = "MY_KV_NAMESPACE"
85
+ # id = "<PRODUCTION_NAMESPACE_ID>"
@@ -54,9 +54,9 @@ const config: TemplateConfig = {
54
54
  configure,
55
55
  transformPackageJson: async () => ({
56
56
  scripts: {
57
- deploy: `${npm} run build && wrangler pages deploy ./build/client`,
58
- preview: `${npm} run build && wrangler pages dev ./build/client`,
59
- "build-cf-types": `wrangler types`,
57
+ deploy: `${npm} run build && wrangler pages deploy`,
58
+ preview: `${npm} run build && wrangler pages dev`,
59
+ "cf-typegen": `wrangler types`,
60
60
  },
61
61
  }),
62
62
  devScript: "dev",
@@ -1,4 +1,4 @@
1
1
  // Generated by Wrangler
2
- // After adding bindings to `wrangler.toml`, regenerate this interface via `npm build-cf-types`
2
+ // After adding bindings to `wrangler.toml`, regenerate this interface via `npm run cf-typegen`
3
3
  interface Env {
4
4
  }
@@ -1,9 +1,20 @@
1
+ #:schema node_modules/wrangler/config-schema.json
1
2
  name = "<TBD>"
2
3
  compatibility_date = "<TBD>"
4
+ pages_build_output_dir = "./build/client"
5
+
6
+ # Automatically place your workloads in an optimal location to minimize latency.
7
+ # If you are running back-end logic in a Pages Function, running it closer to your back-end infrastructure
8
+ # rather than the end user may result in better performance.
9
+ # Docs: https://developers.cloudflare.com/pages/functions/smart-placement/#smart-placement
10
+ # [placement]
11
+ # mode = "smart"
3
12
 
4
13
  # Variable bindings. These are arbitrary, plaintext strings (similar to environment variables)
14
+ # Docs:
15
+ # - https://developers.cloudflare.com/pages/functions/bindings/#environment-variables
5
16
  # Note: Use secrets to store sensitive data.
6
- # Docs: https://developers.cloudflare.com/pages/functions/bindings/#environment-variables
17
+ # - https://developers.cloudflare.com/pages/functions/bindings/#secrets
7
18
  # [vars]
8
19
  # MY_VARIABLE = "production_value"
9
20
 
@@ -49,4 +60,26 @@ compatibility_date = "<TBD>"
49
60
  # Docs: https://developers.cloudflare.com/pages/functions/bindings/#service-bindings
50
61
  # [[services]]
51
62
  # binding = "MY_SERVICE"
52
- # service = "my-service"
63
+ # service = "my-service"
64
+
65
+ # To use different bindings for preview and production environments, follow the examples below.
66
+ # When using environment-specific overrides for bindings, ALL bindings must be specified on a per-environment basis.
67
+ # Docs: https://developers.cloudflare.com/pages/functions/wrangler-configuration#environment-specific-overrides
68
+
69
+ ######## PREVIEW environment config ########
70
+
71
+ # [env.preview.vars]
72
+ # API_KEY = "xyz789"
73
+
74
+ # [[env.preview.kv_namespaces]]
75
+ # binding = "MY_KV_NAMESPACE"
76
+ # id = "<PREVIEW_NAMESPACE_ID>"
77
+
78
+ ######## PRODUCTION environment config ########
79
+
80
+ # [env.production.vars]
81
+ # API_KEY = "abc123"
82
+
83
+ # [[env.production.kv_namespaces]]
84
+ # binding = "MY_KV_NAMESPACE"
85
+ # id = "<PRODUCTION_NAMESPACE_ID>"
@@ -4,8 +4,8 @@
4
4
  "private": true,
5
5
  "scripts": {
6
6
  "deploy": "wrangler deploy",
7
- "dev": "wrangler dev",
8
- "start": "wrangler dev"
7
+ "dev": "wrangler dev --test-scheduled",
8
+ "start": "wrangler dev --test-scheduled"
9
9
  },
10
10
  "devDependencies": {
11
11
  "wrangler": "^3.0.0"
@@ -6,13 +6,20 @@
6
6
  * https://developers.cloudflare.com/workers/platform/triggers/cron-triggers/
7
7
  *
8
8
  * - Run `npm run dev` in your terminal to start a development server
9
- * - Open a browser tab at http://localhost:8787/ to see your worker in action
9
+ * - Run `curl "http://localhost:8787/__scheduled?cron=*+*+*+*+*"` to see your worker in action
10
10
  * - Run `npm run deploy` to publish your worker
11
11
  *
12
12
  * Learn more at https://developers.cloudflare.com/workers/
13
13
  */
14
14
 
15
15
  export default {
16
+ async fetch(req) {
17
+ const url = new URL(req.url)
18
+ url.pathname = "/__scheduled";
19
+ url.searchParams.append("cron", "* * * * *");
20
+ return new Response(`To test the scheduled handler, ensure you have used the "--test-scheduled" then try running "curl ${url.href}".`);
21
+ },
22
+
16
23
  // The scheduled handler is invoked at the interval set in our wrangler.toml's
17
24
  // [[triggers]] configuration.
18
25
  async scheduled(event, env, ctx) {
@@ -1,3 +1,4 @@
1
+ #:schema node_modules/wrangler/config-schema.json
1
2
  name = "<TBD>"
2
3
  main = "src/index.js"
3
4
  compatibility_date = "<TBD>"
@@ -8,9 +9,18 @@ compatibility_date = "<TBD>"
8
9
  [triggers]
9
10
  crons = ["* * * * *"] # * * * * * = run every minute
10
11
 
12
+ # Automatically place your workloads in an optimal location to minimize latency.
13
+ # If you are running back-end logic in a Worker, running it closer to your back-end infrastructure
14
+ # rather than the end user may result in better performance.
15
+ # Docs: https://developers.cloudflare.com/workers/configuration/smart-placement/#smart-placement
16
+ # [placement]
17
+ # mode = "smart"
18
+
11
19
  # Variable bindings. These are arbitrary, plaintext strings (similar to environment variables)
20
+ # Docs:
21
+ # - https://developers.cloudflare.com/workers/wrangler/configuration/#environment-variables
12
22
  # Note: Use secrets to store sensitive data.
13
- # Docs: https://developers.cloudflare.com/workers/wrangler/configuration/#environment-variables
23
+ # - https://developers.cloudflare.com/workers/configuration/secrets/
14
24
  # [vars]
15
25
  # MY_VARIABLE = "production_value"
16
26
 
@@ -100,4 +110,4 @@ crons = ["* * * * *"] # * * * * * = run every minute
100
110
  # Docs: https://developers.cloudflare.com/workers/wrangler/configuration/#vectorize-indexes
101
111
  # [[vectorize]]
102
112
  # binding = "MY_INDEX"
103
- # index_name = "my-index"
113
+ # index_name = "my-index"
@@ -4,8 +4,9 @@
4
4
  "private": true,
5
5
  "scripts": {
6
6
  "deploy": "wrangler deploy",
7
- "dev": "wrangler dev",
8
- "start": "wrangler dev"
7
+ "dev": "wrangler dev --test-scheduled",
8
+ "start": "wrangler dev --test-scheduled",
9
+ "cf-typegen": "wrangler types"
9
10
  },
10
11
  "devDependencies": {
11
12
  "typescript": "^5.0.4",
@@ -6,32 +6,15 @@
6
6
  * https://developers.cloudflare.com/workers/platform/triggers/cron-triggers/
7
7
  *
8
8
  * - Run `npm run dev` in your terminal to start a development server
9
- * - Open a browser tab at http://localhost:8787/ to see your worker in action
9
+ * - Run `curl "http://localhost:8787/__scheduled?cron=*+*+*+*+*"` to see your worker in action
10
10
  * - Run `npm run deploy` to publish your worker
11
11
  *
12
+ * Bind resources to your worker in `wrangler.toml`. After adding bindings, a type definition for the
13
+ * `Env` object can be regenerated with `npm run cf-typegen`.
14
+ *
12
15
  * Learn more at https://developers.cloudflare.com/workers/
13
16
  */
14
17
 
15
- export interface Env {
16
- // Example binding to KV. Learn more at https://developers.cloudflare.com/workers/runtime-apis/kv/
17
- // MY_KV_NAMESPACE: KVNamespace;
18
- //
19
- // Example binding to Durable Object. Learn more at https://developers.cloudflare.com/workers/runtime-apis/durable-objects/
20
- // MY_DURABLE_OBJECT: DurableObjectNamespace;
21
- //
22
- // Example binding to R2. Learn more at https://developers.cloudflare.com/workers/runtime-apis/r2/
23
- // MY_BUCKET: R2Bucket;
24
- //
25
- // Example binding to a Service. Learn more at https://developers.cloudflare.com/workers/runtime-apis/service-bindings/
26
- // MY_SERVICE: Fetcher;
27
- //
28
- // Example binding to a Queue. Learn more at https://developers.cloudflare.com/queues/javascript-apis/
29
- // MY_QUEUE: Queue;
30
- //
31
- // Example binding to a D1 Database. Learn more at https://developers.cloudflare.com/workers/platform/bindings/#d1-database-bindings
32
- // DB: D1Database
33
- }
34
-
35
18
  export default {
36
19
  // The scheduled handler is invoked at the interval set in our wrangler.toml's
37
20
  // [[triggers]] configuration.
@@ -0,0 +1,4 @@
1
+ // Generated by Wrangler
2
+ // After adding bindings to `wrangler.toml`, regenerate this interface via `npm run cf-typegen`
3
+ interface Env {
4
+ }
@@ -1,3 +1,4 @@
1
+ #:schema node_modules/wrangler/config-schema.json
1
2
  name = "<TBD>"
2
3
  main = "src/index.ts"
3
4
  compatibility_date = "<TBD>"
@@ -8,9 +9,18 @@ compatibility_date = "<TBD>"
8
9
  [triggers]
9
10
  crons = ["* * * * *"] # * * * * * = run every minute
10
11
 
12
+ # Automatically place your workloads in an optimal location to minimize latency.
13
+ # If you are running back-end logic in a Worker, running it closer to your back-end infrastructure
14
+ # rather than the end user may result in better performance.
15
+ # Docs: https://developers.cloudflare.com/workers/configuration/smart-placement/#smart-placement
16
+ # [placement]
17
+ # mode = "smart"
18
+
11
19
  # Variable bindings. These are arbitrary, plaintext strings (similar to environment variables)
20
+ # Docs:
21
+ # - https://developers.cloudflare.com/workers/wrangler/configuration/#environment-variables
12
22
  # Note: Use secrets to store sensitive data.
13
- # Docs: https://developers.cloudflare.com/workers/wrangler/configuration/#environment-variables
23
+ # - https://developers.cloudflare.com/workers/configuration/secrets/
14
24
  # [vars]
15
25
  # MY_VARIABLE = "production_value"
16
26
 
@@ -100,4 +110,4 @@ crons = ["* * * * *"] # * * * * * = run every minute
100
110
  # Docs: https://developers.cloudflare.com/workers/wrangler/configuration/#vectorize-indexes
101
111
  # [[vectorize]]
102
112
  # binding = "MY_INDEX"
103
- # index_name = "my-index"
113
+ # index_name = "my-index"
@@ -2,7 +2,6 @@ import { logRaw, updateStatus } from "@cloudflare/cli";
2
2
  import { blue } from "@cloudflare/cli/colors";
3
3
  import { runFrameworkGenerator } from "frameworks/index";
4
4
  import { transformFile } from "helpers/codemod";
5
- import { compatDateFlag } from "helpers/compatDate";
6
5
  import { usesTypescript } from "helpers/files";
7
6
  import { detectPackageManager } from "helpers/packageManagers";
8
7
  import * as recast from "recast";
@@ -40,18 +39,18 @@ const configure = async (ctx: C3Context) => {
40
39
  b.objectExpression([
41
40
  b.objectProperty(
42
41
  b.identifier("preset"),
43
- b.stringLiteral("cloudflare-pages")
42
+ b.stringLiteral("cloudflare-pages"),
44
43
  ),
45
44
  b.objectProperty(
46
45
  b.identifier("rollupConfig"),
47
46
  b.objectExpression([
48
47
  b.objectProperty(
49
48
  b.identifier("external"),
50
- b.arrayExpression([b.stringLiteral("node:async_hooks")])
49
+ b.arrayExpression([b.stringLiteral("node:async_hooks")]),
51
50
  ),
52
- ])
51
+ ]),
53
52
  ),
54
- ])
53
+ ]),
55
54
  ),
56
55
  ]),
57
56
  ];
@@ -66,12 +65,15 @@ const config: TemplateConfig = {
66
65
  id: "solid",
67
66
  displayName: "Solid",
68
67
  platform: "pages",
68
+ copyFiles: {
69
+ path: "./templates",
70
+ },
69
71
  generate,
70
72
  configure,
71
73
  transformPackageJson: async () => ({
72
74
  scripts: {
73
- preview: `${npm} run build && npx wrangler pages dev dist ${await compatDateFlag()} --compatibility-flag nodejs_compat`,
74
- deploy: `${npm} run build && wrangler pages deploy ./dist`,
75
+ preview: `${npm} run build && npx wrangler pages dev`,
76
+ deploy: `${npm} run build && wrangler pages deploy`,
75
77
  },
76
78
  }),
77
79
  compatibilityFlags: ["nodejs_compat"],