npm-publish | GitHub Action to publish to NPM | Runtime Evironment library

Well, I can answer this myself. The way to go was to just add 'cypress' to the devDependencies :)

I managed to do it. With a lot of try and try, here are the key points.

• Package name. It is very important to keep an eye on it. What the documentation does not say it's that the "package.json" need the same name as the registry. If your registry is @foo, your registry need @foo/something as project name. With the code I provide in the script, it takes the root project, and this is the registry.

For me it's https://gitlab.com/gildraen/sushislasher-package so my package.json name is @gildraen/sushislasher-package (though the name seems not important)

So I did it all over again from scratch, with paying more attention to this, and it worked. I really think this was my real mistake: the registry name.

It is possible to commit to Bitbucket repository. You only need to add a script task to execute the git commands.

For below example. I add a powershell task to run below commands in the pipeline to commit changes and push to the Bitbucket repo.