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
fix: ensure that container builds don't disrupt dev hotkey handling
6
+
7
+
currently container builds run during local development (via `wrangler dev` or `startWorker`) prevent the standard hotkeys not to be recognized (most noticeably `ctrl+c`, preventing developers from existing the process), the changes here ensure that hotkeys are instead correctly handled as expected
// All containers running on our platform need to be built for amd64 architecture, but by default docker pull seems to look for an image matching the host system, so we need to specify this here
24
24
"--platform",
25
25
"linux/amd64",
26
26
]);
27
-
// re-tag image with the expected dev-formatted image tag for consistency
@@ -41,8 +52,16 @@ export async function pullImage(
41
52
exportasyncfunctionprepareContainerImagesForDev(
42
53
dockerPath: string,
43
54
containerOptions: ContainerDevOptions[],
44
-
configPath: string|undefined
55
+
configPath: string|undefined,
56
+
onContainerImagePreparationStart: (args: {
57
+
containerOptions: ContainerDevOptions;
58
+
abort: ()=>void;
59
+
})=>void,
60
+
onContainerImagePreparationEnd: (args: {
61
+
containerOptions: ContainerDevOptions;
62
+
})=>void
45
63
){
64
+
letaborted=false;
46
65
if(process.platform==="win32"){
47
66
thrownewError(
48
67
"Local development with containers is currently not supported on Windows. You should use WSL instead. You can also set `enable_containers` to false if you do not need to develop the container part of your application."
@@ -51,17 +70,41 @@ export async function prepareContainerImagesForDev(
0 commit comments