Skip to content
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

Start versioning plugin and Publish to NPM #37

Open
boedy opened this issue May 21, 2019 · 6 comments
Open

Start versioning plugin and Publish to NPM #37

boedy opened this issue May 21, 2019 · 6 comments

Comments

@boedy
Copy link
Collaborator

boedy commented May 21, 2019

We should start versioning this plugin and publishing it NPM to prevent breaking app integrations in the future. Currently there is another plugin with the same name which is occupying the cordova-plugin-webserver namespace. I've reached out to the maintainers to see if its possible to merge the two projects.

If there is no response we should consider publishing it under a different alias. cordova-plugin-http-server perhaps?

@bykof
Copy link
Owner

bykof commented May 21, 2019

I already tried to contact them. I also asked npm to escalate and give me the permission to publish over the name cordova-plugin-webserver, because there wasn't a commit since 30 Nov 2018. Nothing helped...
Let's try again and if nothing will help than we can just publish it over a different name.
cordova-plugin-http-server sounds good in first place

@boedy
Copy link
Collaborator Author

boedy commented Jun 21, 2019

@bykof Got a reply yesterday from the other repo that they've deprecated the plugin and moved the ownership to NPM. They recommend contacting NPM to discuss how to proceed.

@boedy
Copy link
Collaborator Author

boedy commented Jan 10, 2020

@bykof After some back and forth with NPM they we're willing to transfer the cordova-plugin-namespace to me. I recommend that after reviewing open issues and PR's we publish an initial release to NPM.

NPM's response:

The cordova-plugin-webserver package is now all yours now, but you won’t be able to re-use any version numbers used by the previous author. In fact, I'd suggest publishing your first update as a major release, i.e., v1.0.0. Please publish an update to the package as soon as possible with your code.

@bykof
Copy link
Owner

bykof commented Jan 10, 2020

AWESOME! Thank you very much for driving this!

@boedy
Copy link
Collaborator Author

boedy commented Jan 10, 2020

Is this you on NPM? I'll invite you as maintainer.

@bykof
Copy link
Owner

bykof commented Jan 10, 2020

Is this you on NPM? I'll invite you as maintainer.

Yes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants