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
This is not exactly a but, but a limitation to be documented for windows users.
After cloning the repo and installing all packages with npm install, trying to run the project with npm run iterate fails if VCRedist is not installed on Windows 11 (not installed by default on the OS).
This was tested on:
Windows PowerShell 5.1.26100.2161
Windows PowerShell 7.4.6
GitBash (git version 2.47.0.windows.2 + GNU bash, version 5.2.37(1)-release (x86_64-pc-msys))
The following error message appears and the build process hangs (freezes, it doesn't exit with a non 0 return code):
ExperimentalWarning: WASI is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
Expected behavior
The project should build and run
How to reproduce the bug
On any environment listed as tested on this issue description:
1- Clone the repo
2- npm install
3- npm run iterate
Link to the code that reproduces this bug
No response
Extra details
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
After cloning the repo and installing all packages with
npm install
, trying to run the project withnpm run iterate
fails if VCRedist is not installed on Windows 11 (not installed by default on the OS).This was tested on:
Windows PowerShell 5.1.26100.2161
Windows PowerShell 7.4.6
GitBash (git version 2.47.0.windows.2 + GNU bash, version 5.2.37(1)-release (x86_64-pc-msys))
The following error message appears and the build process hangs (freezes, it doesn't exit with a non 0 return code):
Expected behavior
The project should build and run
How to reproduce the bug
On any environment listed as tested on this issue description:
1- Clone the repo
2- npm install
3- npm run iterate
Link to the code that reproduces this bug
No response
Extra details
No response
The text was updated successfully, but these errors were encountered: