Skip to content

feat: add "registry" option for the deploy executor #483

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Feb 19, 2023

Conversation

dmitry-stepanenko
Copy link

@dmitry-stepanenko dmitry-stepanenko commented Feb 19, 2023

PR Checklist

Please check if your PR fulfills the following requirements:

  • Tests for the changes have been added (for bug fixes/features)
  • Docs have been added/updated (for bug fixes/features)
  • Both workspaces were tested Angular and Nx (for bug fixes/features)

What is the current behavior?

Right now there's no ability to deploy to other registries. This might be useful if we want to add another deployment configuration for testing purposes

Issue Number: N/A

What is the new behavior?

Adding the new --registry options for the deploy executor. This will allow to deploy the package into other registries or tools like https://verdaccio.org/docs/what-is-verdaccio/

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

Copy link
Member

@dianjuar dianjuar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome contribution.
Thank you!

@dianjuar
Copy link
Member

Interesting feature!

I could use this feature and verdaccio in my integration test to make them more realistic.

@dianjuar dianjuar merged commit de8bb70 into bikecoders:main Feb 19, 2023
@dianjuar
Copy link
Member

Feature available on ngx-deploy-npm/v/5.2.0

@dmitry-stepanenko
Copy link
Author

@dianjuar thanks for fixing the unit test and merging it!

@dmitry-stepanenko
Copy link
Author

Interesting feature!

I could use this feature and verdaccio in my integration test to make them more realistic.

Totally makes sense, I was considering doing the same with the package I'm working on 🙁

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants