Azure Pipelien fails on npm run build, missing vueapp.key file

Copper Contributor

Hi, I'm having problems with building Vue app in azure pipelines, I do not have experience with NodeJS or Vue, and I'm not sure what is is looking for. Locally my application builds and runs without any problem. Any help would be appreciated 

Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/package/npm
==============================================================================
/usr/local/bin/npm --version
9.8.1
/usr/local/bin/npm config list
; "env" config from environment

userconfig = "/home/vsts/work/1/npm/70.npmrc" 

; node bin location = /usr/local/bin/node
; node version = v18.18.2
; npm local prefix = /home/vsts/work/1/s/testapp1/Prototype.Vue/vueapp
; npm version = 9.8.1
; cwd = /home/vsts/work/1/s/testapp1/Prototype.Vue/vueapp
; HOME = /home/vsts
; Run `npm config ls -l` to show all defaults.
/usr/local/bin/npm run build

> vueapp@0.1.0 build
> vue-cli-service build

 ERROR  Error: ENOENT: no such file or directory, open '/home/vsts/.aspnet/https/vueapp.key'
Error: ENOENT: no such file or directory, open '/home/vsts/.aspnet/https/vueapp.key'
    at Object.openSync (node:fs:603:3)
    at Object.readFileSync (node:fs:471:35)
    at Object.<anonymous> (/home/vsts/work/1/s/testapp1/Prototype.Vue/vueapp/vue.config.js:23:21)
    at Module._compile (node:internal/modules/cjs/loader:1256:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
    at Module.load (node:internal/modules/cjs/loader:1119:32)
    at Module._load (node:internal/modules/cjs/loader:960:12)
    at Module.require (node:internal/modules/cjs/loader:1143:19)
    at require (node:internal/modules/cjs/helpers:119:18)
    at exports.loadModule (/home/vsts/work/1/s/testapp1/Prototype.Vue/vueapp/node_modules/@vue/cli-shared-utils/lib/module.js:86:14)
##[warning]Couldn't find a debug log in the cache or working directory
##[error]Error: Npm failed with return code: 1
Finishing: npm build

 

1 Reply

@tad_boj 

 

Case happened suddenly? Can you try npm cache clean --force