Skip to content

Commit 328cec5

Browse files
author
Github Action
committed
chore: synced pact-js docs
1 parent 9558e33 commit 328cec5

File tree

1 file changed

+19
-0
lines changed

1 file changed

+19
-0
lines changed

website/docs/implementation_guides/javascript/docs/troubleshooting.md

+19
Original file line numberDiff line numberDiff line change
@@ -300,6 +300,25 @@ Users can now use `--ignore-scripts`
300300
- follow the instructions provided
301301
- You can override the path to the pact native build with `PACT_PREBUILD_LOCATION`
302302

303+
### Windows 10 & 11 users
304+
305+
Windows users require a minimum set of tools for building native modules, as part of pact-js's pre-requisites.
306+
307+
If these are not present, the user will be presented with the following message when executing tests.
308+
309+
```
310+
Exception during run: TypeError: Cannot read properties of undefined (reading 'pactffiInitWithLogLevel')
311+
```
312+
313+
In order to install the required tools, there are a couple of ways of doing this, which may vary depending on how you choose to install NodeJS on your machine.
314+
315+
1. With the NodeJS Windows Installer Package
316+
- Ensure you select the following option
317+
- ![Image](https://github.com/user-attachments/assets/1f3bf758-30c5-44a3-a3a3-e3205ef46cd4)
318+
2. If using [nvm-windows](https://github.com/coreybutler/nvm-windows), [nvs](https://github.com/jasongin/nvs), or any other means.
319+
- [See instructions on the node-gyp repository](https://github.com/nodejs/node-gyp?tab=readme-ov-file#on-windows)
320+
321+
For more background detail, see the following [issue](https://github.com/pact-foundation/pact-js-core/issues/608#issuecomment-2698285436)
303322

304323
## ENOENT: no such file or directory, open 'node:path'
305324

0 commit comments

Comments
 (0)