<#1116 Error: Pact publication failed due to windo...
# pact-js-development
g
#1116 Error: Pact publication failed due to windows file path limit exceeded Issue created by SamLeachSky I have enabled the long file paths in windows already. This issue does not happen on mac. If I move the code to a folder with a shorter path, it does not error Software versions • OS: Windows 10 22H2 • Consumer Pact library: 12.1.0 • Provider Pact library: 12.1.0 • Node Version: v18.17.0 Issue Checklist Please confirm the following: ☑︎ I have upgraded to the latest ☑︎ I have the read the FAQs in the Readme ☑︎ I have triple checked, that there are no unhandled promises in my code and have read the section on intermittent test failures • [] I have set my log level to debug and attached a log file showing the complete request/response cycle • [] For bonus points and virtual high fives, I have created a reproduceable git repository (see below) to illustrate the problem Expected behaviour Published successfully Actual behaviour Error: Pact publication failed with non-zero exit code. Full output was: The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail. ❯ ChildProcess. node_modules/.pnpm/@pact-foundation+pact-core@14.0.4/node_modules/@pact-foundation/pact-core/src/publisher.ts12927 ❯ Object.onceWrapper nodeevents629:26 ❯ ChildProcess.emit nodeevents526:35 ❯ ChildProcess.cp.emit node_modules/.pnpm/cross-spawn@7.0.3/node_modules/cross-spawn/lib/enoent.js3429 Steps to reproduce Run on Windows with long file path Relevant log files pact-foundation/pact-js