Skip to content

build: ensure ng-dev command works on windows #25109

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
Jun 18, 2022

Conversation

devversion
Copy link
Member

Apparently the ng-dev command does not work with Git Bash on windows
because of the environment variable being set. We should use ts-node
directly to avoid this issue, and also avoid the $PWD access which
might not work depending on the shell.

Also on the dev-infra side we would need to remove the ts-node shebang
and leave the responsibility to the consumer project.

Apparently the `ng-dev` command does not work with Git Bash on windows
because of the environment variable being set. We should use `ts-node`
directly to avoid this issue, and also avoid the `$PWD` access which
might not work depending on the shell.

Also on the dev-infra side we would need to remove the ts-node shebang
and leave the responsibility to the consumer project.
@devversion devversion requested a review from crisbeto June 18, 2022 12:51
@devversion devversion marked this pull request as ready for review June 18, 2022 12:51
@devversion devversion requested a review from a team as a code owner June 18, 2022 12:51
@devversion devversion added the target: patch This PR is targeted for the next patch release label Jun 18, 2022
@devversion devversion assigned devversion and unassigned devversion Jun 18, 2022
@devversion devversion added the action: merge The PR is ready for merge by the caretaker label Jun 18, 2022
@devversion devversion merged commit e09841c into angular:main Jun 18, 2022
devversion added a commit that referenced this pull request Jun 18, 2022
Apparently the `ng-dev` command does not work with Git Bash on windows
because of the environment variable being set. We should use `ts-node`
directly to avoid this issue, and also avoid the `$PWD` access which
might not work depending on the shell.

Also on the dev-infra side we would need to remove the ts-node shebang
and leave the responsibility to the consumer project.

(cherry picked from commit e09841c)
@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 Jul 19, 2022
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 target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants