huahaofeng
/
aspnetcore
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Workaround issues with Exec + npm when publishing npm packages

This commit is contained in:
Nate McMaster 2019-01-15 16:04:01 -08:00 committed by GitHub
parent d74833c2d7
commit f43a353021
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
build/publish/Publish.csproj
View File

@ -128,7 +128,7 @@
StandardOutputImportance="Normal" /> StandardOutputImportance="Normal" />
<Exec Condition=" @(NpmPackageToPublish->Count()) != 0 " <Exec Condition=" @(NpmPackageToPublish->Count()) != 0 "
Command="npm publish --registry '$(PublishMyGetNpmRegistryUrl)' '%(NpmPackageToPublish.Identity)'" Command="npm publish --registry &quot;$(PublishMyGetNpmRegistryUrl)&quot; &quot;%(NpmPackageToPublish.Identity)&quot;"
ContinueOnError="true"> ContinueOnError="true">
<Output TaskParameter="ExitCode" ItemName="_NpmExitCodes" /> <Output TaskParameter="ExitCode" ItemName="_NpmExitCodes" />
</Exec> </Exec>