Replies: 2 comments
-
|
@juanpicado, let me know if you need more input for this issue. Thanks! |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
@kittaakos I've had no time to look deeply into it yet, but your provided input is quite good 👍 thanks . First time I see this approach. This is on my queue of tasks 📓 . |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the bug
I have different behavior when publishing via the CLI and the Node.js API. I set a repository to demonstrate the issue. For the completeness, I would like to publish a bunch of npm packages to verdaccio and use the private NPM registry when building my electron application.
To Reproduce
Node.js API
Steps to reproduce the behavior:
yarn --cwd ./publisher-node-api && yarn --cwd ./publisher-node-api testIt seems to work when I use the CLI way. But I usually end up with a dangling
verdaccioprocess. I would like to start and stop the server in JS. Is it possible? It seems to work with the CLI way:CLI
Steps to reproduce the behavior:
yarn --cwd ./publisher-cli && yarn --cwd ./publisher-cli testWhat is the preferred way if the Node.js API cannot be used. By the way, It was strange, I had to manually set the
self_pathon the configuration object. See here.If this issue nneeds more context, please let me know.
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions