You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fixup! Update the description of the --local flag for the wrangler dev command to clarify that it disables remote bindings, also un-deprecate and un-hide it
// This should only include logs from the user Wrangler session (i.e. a single list of attached bindings, and only one ready message)
177
-
// Logs order are not deterministic, so we match against to possible outputs.
178
-
constoutput1=dedent`
179
-
Your Worker has access to the following bindings:
180
-
Binding Resource Mode
181
-
env.AI AI remote
182
-
▲ [WARNING] AI bindings always access remote resources, and so may incur usage charges even in local dev. To suppress this warning, set \`remote: true\` for the binding definition in your configuration file.
183
-
⎔ Starting local server...
184
-
[wrangler:info] Ready on http://<HOST>:<PORT>
185
-
[wrangler:info] GET / 200 OK (TIMINGS)`;
186
-
187
-
constoutput2=dedent`
188
-
Your Worker has access to the following bindings:
189
-
Binding Resource Mode
190
-
env.AI AI remote
191
-
▲ [WARNING] AI bindings always access remote resources, and so may incur usage charges even in local dev. To suppress this warning, set \`remote: true\` for the binding definition in your configuration file.
"Your Worker has access to the following bindings:
181
+
Binding Resource Mode
182
+
env.AI AI remote
183
+
▲ [WARNING] AI bindings always access remote resources, and so may incur usage charges even in local dev. To suppress this warning, set \`remote: true\` for the binding definition in your configuration file.
0 commit comments