title: How to link build result of "plain React"/node app with release pipeline
body: <p>To try to make it short, I have a React application that's build on Azure DevOps Build Pipeline like so</p>
  
  <pre><code>trigger:
    - Release
  
  queue:
    name: Hosted
    demands: npm
  
  steps:
    - task: NodeTool@0
      inputs:
      versionSpec: '10.x'
    displayName: 'Install Node.js'
  
  - script: |
    npm ci
    npm run build
    displayName: 'Do npm ci and build'
  </code></pre>
  
  <p>This does what the build would do locally too. Locally the results of build go to <code>build</code> directory (unzipped).</p>
  
  <p>Now when I try to create release pipeline there isn't an artifact to be found using <code>Azure Deploy Web Service</code> task.</p>
  
  <p>If I try to add <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/utility/publish-pipeline-artifact" rel="nofollow noreferrer">PublishPipelineArtifact@0</a> to the build pipeline to create a publication, the YAML editor just tells <em>string does not match pattern...</em> and doesn't let save the definition.</p>
  
  <p>I suppose I should zip the contents of the generated <code>build</code> directory, but what would be the right way? Also, Is using the <code>Azure App Service Deploy</code> task the right way to deploy Azure WebApp? It works for ASP.NET Core apps so it finds the code drop artefact (zipped) and deploys it.</p>
  
  <p>&lt;edit: Adding</p>
  
  <pre><code>- task: PublishPipelineArtifact@0
    inputs:
    artifactName: 'drop'
    targetPath: '$(Build.ArtifactStagingDirectory)/build'
  </code></pre>
  
  <p>Can actually be saved and the build run. Though it errors with</p>
  
  <blockquote>
    <p>2019-01-25T22:42:27.6896518Z ##[section]Starting:
    PublishPipelineArtifact 2019-01-25T22:42:27.6898909Z
    ============================================================================== 2019-01-25T22:42:27.6898962Z Task         : Publish Pipeline Artifact
    2019-01-25T22:42:27.6899006Z Description  : Publish Pipeline Artifact
    2019-01-25T22:42:27.6899034Z Version      : 0.139.0
    2019-01-25T22:42:27.6899062Z Author       : Microsoft Corporation
    2019-01-25T22:42:27.6899090Z Help         : Publish a local directory
    or file as a named artifact for the current pipeline.
    2019-01-25T22:42:27.6899137Z
    ============================================================================== 2019-01-25T22:42:28.0499917Z ##[error]Path not exist: D:\a\1\a\build
    2019-01-25T22:42:28.0708878Z ##[section]Finishing:
    PublishPipelineArtifact</p>
  </blockquote>
  
  <p>&lt; edit 2: It appears removing the <code>/build</code> does the trick. Feels a tad odd since this is what's produced locally. It doesn't produce a zip file which is expected by the release job, namely Azure App Service Deploy.</p>
  
  <p>Have to examine this problem later today (two o'clock at night here). </p>