Microsoft Build Engine升级后无法发布Angular应用程序 [英] Unable to Publish Angular Application After Microsoft Build Engine Upgrade

查看:93
本文介绍了Microsoft Build Engine升级后无法发布Angular应用程序的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

上周的某个时候,Microsoft DevOps从以下版本升级了构建引擎:

Some time last week Microsoft DevOps upgraded the Build Engine from:

用于.NET Core的Microsoft(R)Build Engine版本16.2.32702 + c4012a063

Microsoft (R) Build Engine version 16.2.32702+c4012a063 for .NET Core

TO

.NET Core的Microsoft(R)Build Engine版本16.3.0 + 0f4c62fea

Microsoft (R) Build Engine version 16.3.0+0f4c62fea for .NET Core

似乎这已将NODE更新到版本13,并导致Npm软件包(node-saas)安装停止工作...

It seems that this has update NODE to version 13 and has caused an Npm package (node-saas) installation to stop working...

> node-sass@4.9.3 install D:\a\1\s\Website\ClientApp\node_modules\@angular-devkit\build-angular\node_modules\node-sass
> node scripts/install.js

Downloading binary from https://github.com/sass/node-sass/releases/download/v4.9.3/win32-x64-72_binding.node
Cannot download "https://github.com/sass/node-sass/releases/download/v4.9.3/win32-x64-72_binding.node": 

HTTP error 404 Not Found

升级之前:

 > node-sass@4.9.3 install D:\a\1\s\Website\ClientApp\node_modules\@angular-devkit\build-angular\node_modules\node-sass
 > node scripts/install.js

Downloading binary from https://github.com/sass/node-sass/releases/download/v4.9.3/win32-x64-64_binding.node
Download complete

URL似乎从以下位置更改: https://github.com/sass/node-sass/releases/download/v4.9.3/win32-x64-64_binding.node

It seems like the URL changes from: https://github.com/sass/node-sass/releases/download/v4.9.3/win32-x64-64_binding.node

TO

https://github .com/sass/node-sass/releases/download/v4.9.3/win32-x64-72_binding.node

有人可以帮助解决此问题吗?也许我可以在Azure DevOps中指定引擎版本...

Can someone please help fix this issue? Perhaps I can specify the engine version in Azure DevOps...

推荐答案

我们能够通过在管道中在npm install任务之前添加Use Node.js ecosystem任务来解决构建系统中的此问题.

We were able to resolve this issue in our build system by adding the Use Node.js ecosystem task in our pipeline prior to the npm install task.

  • 在您的开发机器中检查节点环境是否正常运行,做个记录.
  • 将新任务添加到管道中,并搜索"Node.js工具安装程序".
  • 指定要在此任务中使用的节点版本
  • 保存管道

管道yaml类似于以下内容:

The pipeline yaml looks something like the following:

steps:
- task: UseNode@1
  displayName: 'Use Node 8.12.0'
  inputs:
    version: 8.12.0

我们也同时从使用npm install切换到了npm ci,但我不认为此刻它与之相关.更新:我们尝试仅使用npm ci但这并不能解决问题.

We also switched from using npm install to npm ci at the same time, but I don't believe it to be related at this moment. Update: We tried using only npm ci and this did not solve the issue.

这篇关于Microsoft Build Engine升级后无法发布Angular应用程序的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆