I am using npm-publish pipe in my project's pipeline. The problem is that my project's prepublishOnly script requires Node v14 while the npm-publish pipe uses Node v10 (see https://bitbucket.org/atlassian/npm-publish/src/master/Dockerfile).
Does anyone know how I can use Node v14 in the npm-publish pipeline?
name: Build and Publish
- npm config set unsafe-perm true
- npm install email@example.com firstname.lastname@example.org -g
- npm install
- pipe: atlassian/npm-publish:0.3.2
EXTRA_ARGS: "--dry-run --unsafe-perm"
Relevant error in my pipeline log:
Status: Downloaded newer image for bitbucketpipelines/npm-publish:0.3.2
INFO: Starting pipe execution...
INFO: Registry URL: https://registry.npmjs.org
INFO: Setting npm auth configuration...
INFO: Publishing package...
npm publish . --dry-run --unsafe-perm
> email@example.com prepublishOnly .
> NODE_ENV=production webpack --config=./webpack.module-build.config.js
[webpack-cli] Failed to load '/opt/atlassian/pipelines/agent/build/webpack.module-build.config.js' config
[webpack-cli] Error: Missing binding /opt/atlassian/pipelines/agent/build/node_modules/node-sass/vendor/linux_musl-x64-64/binding.node
Node Sass could not find a binding for your current environment: Linux/musl 64-bit with Node.js 10.x
Found bindings for the following environments:
- Linux 64-bit with Node.js 14.x
This usually happens because your environment has changed since running `npm install`.
"prepublishOnly": "NODE_ENV=production webpack --config=webpack.module-build.config.js"
On October 20, 2021, Atlassian published a security advisory for Jira Service Management. The full advisory is available at this link. We've seen a number of questions already asking for...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events