How can I publish an existing package from my node_modules to the registry

First of all , I am sorry if I am approaching this wrong or I missed some docs or any relevant info

Is your feature request related to a problem? Please describe. It is not a feature request though but still using this template It is more like better usage docs

I have installed this and as mentioned in the docs, set the npm registry to verdaccio and also added the profile and user. now how do I publish a package from my node_modules to here. I tried by navigating to my project directory which is having package.json and ran the verdaccio publish command but it telling please update the version of the package. Here how can I update the 3rd party package’s version which is not even built. Like I am doing this for @bable/core and I really dont want to change the package.json version property for this package from my node_modules

Describe the solution you’d like A clear and concise description of what you want to happen. writing better docs for the usage sections

Describe alternatives you’ve considered A clear and concise description of any alternative solutions or features you’ve considered. None Additional context Add any other context or screenshots about the feature request here.

[LOLdevelopr]

Thats what, I was approaching this all in wrong way I thought we can publish an existing package without bumping the version. Okay This clarifies a lot Again thanks a lot

[juanpicado]

@LOLdevelopr you need to be your your process follow the following constrains.

• The version you are trying to publish does not exist in any of the uplinks (which if you are using the default one will be the case @babel/core@7.4.4. ✅

• Uplinks if the package access match '@*/*' must not contains a proxy property.

If you cannot afford any of those above. Then the last option is create a specific package section for @babel/core without proxy.

 '@babel/core':
    access: $all
    publish: $authenticated
   unpublish: $authenticated
 '@*/*':
    # scoped packages
    access: $all
    publish: $authenticated
    unpublish: $authenticated
    proxy: npmjs

Reminder, the order is important, your section always above the default one

Verdaccio always check on publish wether the version you are trying to publish already exist in ANY o the uplinks defined in the proxy section, if such case is positive, then you get EPBULSIHCONFLICT error.