Publish to NPM

[verdaccio]

Publish to NPM

[ofbeaton]

also readme needs to be updated with install instructions, still points to sinopia

[trentearl]

Tests are passing on travis but not locally on on OSX for 0.1.0. I think this is just because the tests are running by starting the server in a new process. I am trying to get the server in test to start in the same process.

After this is complete I will run through the documentation and publish

[trentearl]

I have prepared the release for 1.0.0.

Unfortunately user lonelyclick has published verdaccio without informing anyone. This prevents me from publishing

I have emailed the user asking what there intentions are and if I can be collaborat

[jmwilkinson]

Is he a member of the verdaccio organization? Also can you make the members public?

[trentearl]

lonelyclick is not, I searched through the issues and my email and found no activity from that user at all.

The only member is aeweidne, and I had accidentally set that user to be on the repo and not the organization. I just sent aeweidne an invitation to be a member of the group. Unless I'm misunderstanding Github wont allow me to make members public with out any members

[jmwilkinson]

Interesting. From some quick googling, it appears that individuals must choose to appear as public.

On a related note, a big reason I wanted verdaccio to be its own organization would be so that we wouldn't run into the situation where the project depends on one person. In that vein, would you mind adding rlidwka, as he has committed a lot to the project, and myself- while I don't have much time to give, my company has a vested interest in making sure support is ongoing, so I can help make sure it doesn't die.

[trentearl]

Yes I agree, that is a good idea. Both of you have been invited

[trentearl]

2.0.1 is publish

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.