TFS 2017内部部署无法在cmd中找到节点模块 [英] TFS 2017 on-premise cannot find node modules in cmd

查看:62
本文介绍了TFS 2017内部部署无法在cmd中找到节点模块的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述


如何在作为服务运行的tfs代理中运行npm模块?



这是我的设置。



我在本地机器上设置代理,TFS 2017在本地运行。我尝试在作为服务运行的代理上构建aurelia应用程序。我已经在代理运行的机器中安装了node,aurelia cli和npm。全局访问手动运行
cmd命令  au
build
(aurelia cli build)。但是,当我创建一个命令行构建步骤运行  au (工具)
和  build (参数)
代理商找不到au。



我认为它也找不到其他的npm模块。

解决方案

嗨JMV Trinidad,



感谢您在此发帖。



根据堆栈溢出中的线程:


http://stackoverflow.com/questions/43182751/tfs-2017-on-premise-cannot-find-node-modules-in-cmd


您已在starain的帮助下更改了服务帐户,从而解决了问题。那么,您可以在此处发布您的解决方案,然后将其标记为答案,这将对与您有同样问题的其他用户有所帮助。感谢您的理解。:)



最好的问候


Limitxiao Gao


How to run npm modules in tfs agent running as a service?

Here's my setup.

I setup agent on local machine with TFS 2017 running on-premise. And I try to build aurelia application on agent running as a service. I already have installed node, aurelia cli and npm in machine where the agent run. It was globally accessed running manually cmd with command au build(aurelia cli build). However when I create a Command Line build step running au(Tool) and build(Arguments) the agent does not find au.

I think it will also not find other npm modules.

解决方案

Hi JMV Trinidad,

Thank you for posting here.

According to your thread in Stack overflow:

http://stackoverflow.com/questions/43182751/tfs-2017-on-premise-cannot-find-node-modules-in-cmd

You have solved the problem by changing the service account with the help of starain. So could you please post your solution here, then mark it as answer, it will be helpful for other users who get the same issue as you. Thank you for your understanding.:)

Best Regards

Limitxiao Gao


这篇关于TFS 2017内部部署无法在cmd中找到节点模块的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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