[英]Semantic-UI Dependency Stuck on Ongoing Build on Azure Devops Pipelines
According to the document , we can know: The first time you run gulp you will be greeted with an interactive installer, as far as I know, the pipeline cannot handle such interactive setup.根据文档,我们可以知道:第一次运行 gulp 时,您会看到一个交互式安装程序,据我所知,管道无法处理这种交互式设置。
The easiest way to install Semantic UI is our NPM package which contains special install scripts to make setup interactive and updates seamless.
安装 Semantic UI 的最简单方法是我们的 NPM package,其中包含特殊的安装脚本,可使设置交互并无缝更新。
The install process will create two files: semantic.json
stores paths for your build and sits on the top-level of your project, theme.config
is a LESS file that exists in src/
and allows you to centrally set the themes for each UI component.安装过程将创建两个文件:
semantic.json
存储构建路径并位于项目的顶层, theme.config
是一个 LESS 文件,存在于src/
中并允许您集中设置每个 UI 的主题零件。
The installer will also create a special folder which contains your site-specific themes.安装程序还将创建一个特殊文件夹,其中包含您的站点特定主题。 The default location for this is
src/site
.默认位置是
src/site
。 For details, please refer to this document .有关详细信息,请参阅此文档。
So a workaround I can think of is that you can run the npm install semantic-ui --save
command locally, and then publish the generated files from the local to the azure repo.所以我能想到的解决方法是,你可以在本地运行
npm install semantic-ui --save
命令,然后将生成的文件从本地发布到 azure repo。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.