--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/third_party/emsdk/emsdk.bat	Thu Jan 22 21:23:17 2026 -0800
@@ -0,0 +1,53 @@
+@echo off
+
+:: Find python from an explicit location relative to the Emscripten SDK.
+
+setlocal
+
+:: When using our bundled python we never want the users
+:: PYTHONHOME or PYTHONPATH
+:: https://github.com/emscripten-core/emsdk/issues/598
+
+if exist "%~dp0python\3.13.3_64bit\python.exe" (
+  set EMSDK_PY="%~dp0python\3.13.3_64bit\python.exe"
+  set PYTHONHOME=
+  set PYTHONPATH=
+  goto end
+)
+
+if exist "%~dp0python\3.9.2_64bit\python.exe" (
+  set EMSDK_PY="%~dp0python\3.9.2_64bit\python.exe"
+  set PYTHONHOME=
+  set PYTHONPATH=
+  goto end
+)
+
+if exist "%~dp0python\3.9.2-nuget_64bit\python.exe" (
+  set EMSDK_PY="%~dp0python\3.9.2-nuget_64bit\python.exe"
+  set PYTHONHOME=
+  set PYTHONPATH=
+  goto end
+)
+
+:: As a last resort, access from PATH.
+set EMSDK_PY=python
+
+:end
+call %EMSDK_PY% "%~dp0\emsdk.py" %*
+
+:: If emsdk returned with error code >= 1, then skip executing emsdk_set_env
+:: below.
+if ERRORLEVEL 1 (
+  endlocal
+  exit /b %ERRORLEVEL%
+)
+
+endlocal
+
+:: python is not able to set environment variables to the parent calling
+:: process, so therefore have it craft a .bat file, which we invoke after
+:: finishing python execution, to set up the environment variables
+if exist "%~dp0\emsdk_set_env.bat" (
+  call "%~dp0\emsdk_set_env.bat" > nul
+  del /F /Q "%~dp0\emsdk_set_env.bat"
+)