Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: node doesn't run .bat files on windows #504

Merged
merged 1 commit into from
May 8, 2024
Merged

fix: node doesn't run .bat files on windows #504

merged 1 commit into from
May 8, 2024

Conversation

timvahlbrock
Copy link
Contributor

PR Template

Fixes #503

@timvahlbrock
Copy link
Contributor Author

@mefellows wasn't able to test this so far, as I didn't have the time to set up the project completely.

@timvahlbrock
Copy link
Contributor Author

Problem was that I don't have the binary SDK so I didn't have access to the original .bat files. However, I just tested it by creating a dummy .bat file manually and everything works as expected.

@mefellows
Copy link
Member

Thanks @timvahlbrock

Problem was that I don't have the binary SDK

What do you mean by this - the standalone tools aren't there? The developer guide has some steps on setting this up for your local.

@mefellows
Copy link
Member

Looks like lint failure. Can you please run npm run format:fix and then commit/rebase your changes?

@timvahlbrock
Copy link
Contributor Author

Thanks @timvahlbrock

Problem was that I don't have the binary SDK

What do you mean by this - the standalone tools aren't there? The developer guide has some steps on setting this up for your local.

Yeah got some errors on npm install relating to Node-Gyp, so I assumed I needed the Native SDK to get the .bat files, which makes little sense in hindsight. Didn't spot the DEVELOPER.md file though (maybe add this to the Contributing section of the README?), but tried to run npm run download-libs script. This failed because windows assumes bash means the bash in my WSL, same problem occurs with the Instructions in the DEVELOPER.md . Just used the Git Bash Terminal in VSCode to run the prebuild script. Another possibility would be to explicitly specify the path to the git bash. The .bat files are now there; I reverified that the changes work as intended.

Will fix the prettier errors in a minute.

@timvahlbrock
Copy link
Contributor Author

should be good.

@mefellows
Copy link
Member

Thanks, yes the development environment is probably not super Windows friendly. Sorry about that.

If the build passes, I'll get this merged and released ASAP.

@mefellows mefellows merged commit 4f125b3 into pact-foundation:master May 8, 2024
19 checks passed
@YOU54F YOU54F mentioned this pull request May 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

No output due to EINVAL on Windows
2 participants