-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Bikeshed discussion: package name #36
Comments
Moving to the reduxjs GitHub organization is clearly a win, though I think we should stick with unscoped packages to be consistent with Redux's own package name. Alternatively if you want to use npm organizations, we could move Redux to @timdorr I notice you own redux-start on npm and it appears to be parked. Could we use it or do you need it for something else? |
Awesome, |
I would second |
Let's see if we can get |
I'm not against using the |
I vote we optimize for shipping. It doesn't seem like anyone here has a terribly strong opinion one way or the other and I'd rather start promoting an easy way to get started with redux than worry about what we call it. |
@markerikson What do you think about switching to |
I would like to suggest ReduxKit. Inspiration: UIKit, ARKit, WatchKit, etc. |
I like that name, but |
@markerikson Do you want to move this repo into @reduxjs and change the name to redux-start? If you can't do that for some reason, let me know and I'll fiddle with the knobs so you can. |
@nickmccurdy it's not |
|
Yep, the big problem with that is that the name is already taken on NPM: https://www.npmjs.com/package/redux-starter-kit . We'd have to ask the author for it. |
|
@shotaK Can you donate the redux-starter-kit package name to us? |
I just sent a dispute email to NPM asking about possibly getting |
afaik npm generally waits 2 weeks, and if the owner doesn't respond, they give you the namespace |
Yes, I am OK to donate it. How should we proceed? |
@shotaK Can you add @markerikson as a maintainer on npm? He's |
@timdorr Done. |
Awesome. @shotaK, thank you very much - really appreciate it! Okay, in that case, I'm inclined to just go with |
Oooo-kay, I just hit the button to transfer this repo to the I suppose we can debate a bit further whether we would want |
I feel like this is silly to say because I don't have a specific reason beyond familiarity bias, but I do think scoped packages should be left to addons/plugins/exts/etc. I think this is worthy of it's own distinct repo. ps shoutout to @shotaK - super cool of you to do that Edit: I might pull back my above 1st comment. I guess there really is no down or upside to one over the other. |
In lieu of us actually having control over |
@timdorr : awright, works for me! In that case, I'll declare the issue as settled unless a compelling reason comes up to change it. Long live
|
We can transition later, but from what I've seen from Babel 7, there's quite a lot of overhead, especially if your package is frequently used as a peerDependency. Are there plans to use the |
Not at the moment. I don't want to plan out anything that's contingent on the opaque decision process within npm, Inc. |
Sorry I think I got confused, do we still not have |
No, we don't. Tim said he has |
Package/org names with |
Time for a lovely bikeshed discussion on what exactly we should name this package!
At the moment, the repo is located under my Github (
markerikson/redux-starter-kit
), and published as a scoped NPM package under my username (@acemarke/redux-starter-kit
).I've always said that I want to turn this into an official Redux-branded package. That first means moving it to our new
reduxjs
Github org, which is a no-brainer. (In fact, could probably do that any time now.)However, there's two questions beyond that:
There's already NPM packages called
redux-starter-kit
(an app boilerplate project) andredux-boost
(which is kinda similar to this package, but also does some data fetching stuff), so it looks like both of those are non-options. (Unless we were to convince the owners to give us the package names or something.)So, I'm open to suggestions for final package naming and publishing.
/cc @nickmccurdy , @sw-yx , @matthew-gerstman, and whoever else feels like commenting.
The text was updated successfully, but these errors were encountered: