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
the worker scripts are now compatible with nodejs worker threads: https://nodejs.org/api/worker_threads.html
the worker tests now use node worker threads instead of a browser
removes dependency to puppeteer
# BEGIN Standard MS Devcontainer for Typescript-Node
6
6
7
7
# See here for image contents: https://github.com/microsoft/vscode-dev-containers/tree/v0.155.1/containers/typescript-node/.devcontainer/base.Dockerfile
8
8
# [Choice] Node.js version: 14, 12, 10
9
-
ARG VARIANT="16-buster"
10
-
FROM mcr.microsoft.com/vscode/devcontainers/typescript-node:0-${VARIANT}
9
+
ARG VARIANT="22-bullseye"
10
+
FROM mcr.microsoft.com/vscode/devcontainers/typescript-node:1-${VARIANT}
11
11
12
12
# [Optional] Uncomment if you want to install an additional version of node using nvm
13
13
# ARG EXTRA_NODE_VERSION=10
@@ -24,7 +24,7 @@ FROM mcr.microsoft.com/vscode/devcontainers/typescript-node:0-${VARIANT}
24
24
# Install EMSDK to /emsdk just like the EMSDK Dockerfile: https://github.com/emscripten-core/emsdk/blob/master/docker/Dockerfile
25
25
ENV EMSDK /emsdk
26
26
# We pin the EMSDK version rather than 'latest' so that everyone is using the same compiler version
27
-
ENV EMSCRIPTEN_VERSION 3.1.64
27
+
ENV EMSCRIPTEN_VERSION 4.0.5
28
28
29
29
RUN git clone https://github.com/emscripten-core/emsdk.git $EMSDK
30
30
@@ -68,38 +68,4 @@ RUN echo ". /emsdk/emsdk_env.sh" >> /etc/bash.bashrc
68
68
RUN echo 'export EM_NODE_JS="$EMSDK_NODE"' >> /etc/bash.bashrc
# Here we install all of the packages depended upon by Chrome (that Puppeteer will use for headless tests).
76
-
# We could also take a page from https://github.com/buildkite/docker-puppeteer/blob/master/Dockerfile instead,
77
-
# and install the latest stable version of Chrome to get the right dependencies, but that version changes over time,
78
-
# so the stable version of Chrome and the version installed by Puppeteer might diverge over time.
79
-
# It also means they end up having Chrome downloaded and installed twice.
80
-
# We could install the particular version of Chrome that our version of Puppeteer would use and then tell Puppeteer not to download its own version of Chrome,
81
-
# but then we'd have to rebuild our Docker container every time we revved Puppeteer, and that feels fiddly too.
82
-
# For all of these reasons, it seems safer to simply install the explicit list packages depended upon by Chrome, assume that's unlikely to change
# Installs the command "sha3sum", which is used check the download integrity of sqlite source.
95
-
&& apt-get install -y libdigest-sha3-perl \
96
-
&& rm -rf /var/lib/apt/lists/*
97
-
98
-
# We set this env variable (RUN_WORKER_TEST_WITHOUT_PUPPETEER_SANDBOX=1) this to tell our sql.js test harness to run Puppeteer without the sandbox.
99
-
# Otherwise, when we instantiate Puppeteer, we get this error:
100
-
# Puppeteer can't start due to a sandbox error. (Details follow.)
101
-
# [0321/173044.694524:FATAL:zygote_host_impl_linux.cc(117)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/master/docs/linux/suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
0 commit comments