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

Chat about transferring npm package name? #54

Open
samselikoff opened this issue Sep 18, 2019 · 2 comments
Open

Chat about transferring npm package name? #54

samselikoff opened this issue Sep 18, 2019 · 2 comments

Comments

@samselikoff
Copy link

Hi there!

I am working on an npm package over at @miragejs/server, which is an extraction of an existing project I've worked on for four years called Ember CLI Mirage.

As I was going to publish the new core package to npm I looked at some the existing "mirage" related names, and came across this package. I pulled it up and it looks like the latest version was published about 2 years ago.

So, I wanted to reach out and ask – is there any chance you'd be open to transferring the mirage npm package name? I would still keep my project over at the @miragejs org, but I'd be able to publish my package to the mirage npm name.

It would mean so much to me to be able to get this name for my project 🙏 I've been putting a lot of effort into my extraction, and I would be so excited if I could tell folks to npm install mirage!

Let me know what you think, and hope you have a great day!

@lpinca
Copy link
Member

lpinca commented Sep 20, 2019

This is an official plugin of the Primus project so I don't think we can do that.

cc: @3rd-Eden

@samselikoff
Copy link
Author

Ah – didn't realize that.

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