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
feat: run server init as promise #3210
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The way to use verdaccio programatically is not very friendly if you are using
as this example.
runServer
) forbid this and only allows the first one listener listed🚀 Feature
runServer
method to run verdaccio programatically as a promiseOn v6 #2165 this was improved and I am moving the same API to v5 so is much easier to migrate in the future.
There are three ways to use it:
config.yaml
as is you would runverdaccio
in the consoleWith an object you need to add
self_path
, manually (it's not nice but would be a breaking change changing it now) on v6 this is not longer need it.parseConfigFile
methodExposed for easy use parse a
yaml
file as an object