Skip to content

fix(build): binary execution on windows #1675

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

Merged
merged 1 commit into from
Nov 3, 2016

Conversation

devversion
Copy link
Member

Currently the `execNodeTask` helper function resolves the binary from the `package.json` and spawns a new process of it.

Specifically on Windows this will break, because the Windows Shell does not know how to run the given files (from the Shebang or PATHEXT)

Since those binaries are always node binaries we could manually run the node interpreter and run the given JS file as an argument.


  • Fixes a few lint issues (when running it on the task_helpers.ts file as well)
  • Ensures that the execNodeTask function works on Windows as well (fixes gulp e2e and gulp build:release on windows)

Closes #1129

Currenlty the `execNodeTask` helper function resolves the binary from the `package.json` and spawns a new process of it.

Specifically on Windows this will break, because the Windows Shell does not know how to run the given files (from the Shebang or PATHEXT)

Since those binaries are always node binaries we could manually run the node interpreter and run the given JS file as an argument.

Closes angular#1129
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Nov 1, 2016
@jelbourn
Copy link
Member

jelbourn commented Nov 2, 2016

R: @hansl

@hansl
Copy link
Contributor

hansl commented Nov 3, 2016

LGTM.

@jelbourn jelbourn added the action: merge The PR is ready for merge by the caretaker label Nov 3, 2016
@jelbourn jelbourn merged commit e3882fc into angular:master Nov 3, 2016
@devversion devversion deleted the chore/task-helpers-windows branch November 3, 2016 22:58
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Building release via Gulp fails on Windows
4 participants