Hello guys, Bitbucket pipelines were working really very good. I was on vacation 2 weeks and didnt deploy anything that time. When I arrive I detected that Pipiline is failed every time. I thought that it happened after my changes, but after I tried to build my another branch which was working, and its failing also. I ran the command with verbose and detected that I am getting really very strange error:
```
> NX Unknown package manager: undefined
HookWebpackError: Unknown package manager: undefined
at makeWebpackError (/opt/atlassian/pipelines/agent/build/node_modules/webpack/lib/HookWebpackError.js:48:9)
at /opt/atlassian/pipelines/agent/build/node_modules/webpack/lib/Compilation.js:3068:12
at eval (eval at create (/opt/atlassian/pipelines/agent/build/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:71:1)
at fn (/opt/atlassian/pipelines/agent/build/node_modules/webpack/lib/Compilation.js:481:17)
at _next0 (eval at create (/opt/atlassian/pipelines/agent/build/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:69:1)
at eval (eval at create (/opt/atlassian/pipelines/agent/build/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:82:1)
at eval (eval at create (/opt/atlassian/pipelines/agent/build/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:14:1)
-- inner error --
Error: Unknown package manager: undefined
at getLockFileName (/opt/atlassian/pipelines/agent/build/node_modules/nx/src/plugins/js/lock-file/lock-file.js:109:11)
at /opt/atlassian/pipelines/agent/build/node_modules/@nx/webpack/src/plugins/generate-package-json-plugin.js:42:64
at fn (/opt/atlassian/pipelines/agent/build/node_modules/webpack/lib/Compilation.js:479:10)
at _next0 (eval at create (/opt/atlassian/pipelines/agent/build/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:69:1)
at eval (eval at create (/opt/atlassian/pipelines/agent/build/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:82:1)
at eval (eval at create (/opt/atlassian/pipelines/agent/build/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:14:1)
Hi Giorgi and welcome to the community!
I would suggest checking the steps in the following guide, specifically Scenario 1: Builds were successful earlier, but started failing recently:
This includes possible causes and troubleshooting steps you can follow. If you still cannot figure it out, you can post the build URLs in the support ticket you created, and the engineer working on your ticket can help you with troubleshooting.
Please feel free to reach out if you have any questions.
Kind regards,
Theodora
For anyone that may have Node or NPM issues. What happened to us these passed few days was that the BitBucket Pipelines image it uses, for whatever reason, started using a very old version of Node and our NPM install process was failing. So we had to update our bitbucket pipelines YAML file to tell their system which version of Node to use. This solved our issue.
Docs:
https://support.atlassian.com/bitbucket-cloud/docs/javascript-nodejs-with-bitbucket-pipelines/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.