microsoft / microsoft/TypeScript

Container builds fails after upgrade to Microsoft.TypeScript.MSBuild 5.2.2

Open
#55,886 3 comments 0 reactions 1 assignee View on GitHub

@joj is already working on this.

Since Oct 3, 2023.

Needs Investigation
Dominant language
Go
Stars
111k
Forks
14.4k
Avg merge
1d 19h
Merged PRs (30d)
117

Description

🔎 Search Terms

Microsoft.TypeScript.MSBuild error MSB6006: "/usr/bin/nodejs" exited with code 1

🕗 Version & Regression Information
  • This is a crash
  • This changed between versions 5.0.4 and 5.2.2
⏯ Playground Link

No response

💻 Code
FROM --platform=$BUILDPLATFORM mcr.microsoft.com/dotnet/sdk:7.0 AS build
WORKDIR /src
RUN apt-get update \
    && apt-get install -y --no-install-recommends \
        nodejs \
        npm \
    && rm -rf /var/lib/apt/lists/*
COPY ["*.csproj", "package*", "tsconfig.json", "."]
RUN --mount=type=cache,id=npm,target=/root/.npm --mount=type=cache,id=nuget,target=/root/.nuget/packages dotnet restore
RUN --mount=type=cache,id=npm,target=/root/.npm --mount=type=cache,id=nuget,target=/root/.nuget/packages npm install
🙁 Actual behavior

[xxx build 8/10] RUN --mount=type=cache,id=npm,target=/root/.npm --mount=type=cache,id=nuget,target=/root/.nuget/packages dotnet build:
10.86 MSBuild version 17.7.3+8ec440e68 for .NET
12.15 Determining projects to restore...
12.47 All projects are up-to-date for restore.
13.19 /root/.nuget/packages/microsoft.typescript.msbuild/5.2.2/tools/Microsoft.TypeScript.targets(485,5): error MSB6006: "/usr/bin/nodejs" exited with code 1. [/src/xxx.csproj]
13.21
13.21 Build FAILED.
13.21
13.21 /root/.nuget/packages/microsoft.typescript.msbuild/5.2.2/tools/Microsoft.TypeScript.targets(485,5): error MSB6006: "/usr/bin/nodejs" exited with code 1. [/src/xxx.csproj]
13.21 0 Warning(s)
13.21 1 Error(s)
13.21
13.21 Time Elapsed 00:00:02.13

🙂 Expected behavior

build success

Additional information about the issue

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.