Option to ignore packages already published error about ngx-deploy-npm

[dianjuar]

Got it.
So you are using a strategy that sometimes your package is being published with a version that is already up there, that is ok to you and you just want to ignore the error.

This makes sense, otherwise, you will have to implement a validation to avoid publishing a version that is already there and make it viable in a mono-repo environment. Also, modify the CI to do not launch an error because that is the expected result.

---

That is the spirit of this executor/builder to automate repeatable things related to package publishing.

Thank you so much, good first issue.

[dianjuar]

A quick note about the original feature request, I think the ability to call ngx-deploy-npm:deploy right after @jscutlery/semver:version succeed, would fix the "package already published" error more reliably than adding an option to ignore NPM errors.

I agree that jscutlery/semver#167 would be better than implement a new option to ignore errors. We are having already a discussion (#73) to integrate both tools.

When we consider that both tools are holding hands I'm going to close this issue.

[dianjuar]

The implementation of Semver has been tested successfully.

Please use the post-targets Semver's feature

--

A configuration example will be soon on the readme.
In the meantime, you can find an example configuration on the discussion #73. Another example is in our workspace

[dianjuar]

Hello Gentlemens 🎩

I love the discussion generated here. You are bringing several good and exciting points, it's difficult to keep track of this here (on an issue), so, I created the discussion #73 to group all subjects/issues regarding the integration with Semver.

I going to migrate the points mentioned here to talk about them in their own space.
If you have another, it's more than welcome.

[dianjuar]

@edbzn seems like your plugin and ours are natural allies. I'm seriously considering referencing yours in the Version Bumping Readme section.

---

It's not the first time that this tool has something to do with Semver, take a look at this -> #66

[edbzn]

Hi there,

We are planning to include support of package publishing in @jscutlery/semver v3. We want to provide a fully automated release cycle in the CI (releasing + publishing), the idea is to add the ability to call another builder/executor whenever semver succeeds to bump a package, in our case ngx-deploy-npm:deploy.

The related issue is here jscutlery/semver#167, note that I already started working on it. I would love to get your feedback guys.

I can already see conflicting things between ngx-deploy-npm and @jscutlery/semver, this option --package-version for example can conflict/override what semver did just before.

I think we would need to work together @dianjuar to make both executors compatible and reliable, what do you think?

[edbzn]

A quick note about the original feature request, I think the ability to call ngx-deploy-npm:deploy right after @jscutlery/semver:version succeed, would fix the "package already published" error more reliably than adding an option to ignore NPM errors.

[spaceribs]

This is definitely an interesting problem that I'm not sure has an existing architectural pattern within Nx/Angular tasks, @edbzn task essentially creates a different affected graph which should be communicated over to the publish task. We could create a post/pre action as a configuration to either one of your plugins but I feel like that may be an anti-pattern?

both your plugins are amazing for what they do, and version bumping/publishing are pretty well delineated. What i'm saying is, I'd like to make sure these libraries focus on doing one thing really well. Who know what sort of storage I'd actually like to send my package to (github releases?) and who knows what sort of semantic versioning strategy I'd like to implement.