-
Notifications
You must be signed in to change notification settings - Fork 56
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
Questions before contributing #65
Comments
Hello, thanks for participating in the project!
|
Sorry I didn't fully answer your plugins question: yes, that might be the case. Although as of today we hadn't found any issues, it could happen. I'll open an issue to track this. |
My soul was just sold 😆 . Yes, hopefully we finish the UI along February and couple of things and we can launch a beta with no further additions for a month. Then, big release. |
Thanks for explainations! In the meantime, I will try to build a Docker image on top of 3.x version, because my company is always afraid of potential incompatibilities. Will watch for v4 and will try to add my planned features on v4.x. |
closing this as we are on 4 now |
I'd like to add some features on this package, but I have some questions before contributing.
Could you explain why we initialize a global tunnel in
src/verdaccio.js
?I see despite the fact we use verdaccio
3.x
inpackage.json
dependencies, we build docker image using4.x-next
base verdaccio docker image. Could this cause instability because we build a plugin for an older version of verdaccio than the one used in the base docker image?The text was updated successfully, but these errors were encountered: