I'm un-maintaining local-npm #122
Conversation
[skip ci]
|
And thanks also of course to @NickColley for the logo and really every other contributor; y'all are wonderful. :) |
|
Thanks for the great project @nolanlawson, and I agree with all your points, time to move on <3 |
|
Thanks a lot for the project and the work you put in @nolanlawson (and others contributors). Have fun playing and maintaining other cool stuff! :) |
|
I'm not so eager to let this project whither. Of all the self-hosted npmjs mirrors I've found, only this one and npm_lazy are active projects. npm-mirror, sinopia, reggie, reginabox... none have been updated in over a year. Plus, this one has a web UI. Maybe I see the project differently, because I've come to it out of a business need; npmjs.org screws up enough that I've decided I need a caching server in-datacenter for continuous integration. Briefly here's my thoughts:
I don't need that support, I just need a reliable mirror
Again, I guess I'm not interested in full read/write, just read.
That one would actually be really cool. Particularly in combination with my continuous integration and something like next-update.
That's just an npm install flag though, right? Wouldn't that be useless on a fresh docker image, for example? One huge advantage of running a local-npm server is that I can share the cached results between all the computers in my company. I'm also hoping that every package that any employee (or CI server) installs can be cached, so that "left-pad" style scenarios where "npm install worked yesterday, but today it doesn't" can be avoided. Thoughts? |
|
@wmhilton you are welcome to start maintaining it 😄 |
|
Yeah I just don't have time or energy for this project anymore, sorry. Please feel free to fork or open PRs as desired. |
|
I just found this gem (reading https://addyosmani.com/blog/using-npm-offline/), so finding that is not maintained any more was a bit disappointing. However, I strongly agree with @wmhilton that
is not applicable in my scenarios for using What about this: if
I believe that just Monterey can extend the |
|
@adriatic @nolanlawson The original author and I came to an agreement to leave this project unmaintained (see the discussion here #127) and I started a fork under a new name registry-alpha. I would love to have a reason to develop it further! Tell you what, could you open an issue on registry-alpha to tell me more about Monterey's goals and how they involve registries? |
|
@wmhilton @nolanlawson My plans are even more ambitious than Will's but at this point this is not as important as knowing that npm-local "fits the bill" just as is. So, I would hate to make yet another fork and further dilute the very impressive code that Nolan created. Given the area of interest that @wmhilton shares (list of GitHub repositories) I would not be surprised to see him (Will) to work on Will, please join me in this Gitter chat room to discuss these issues, if you are interested |
|
@nolanlawson would you be interested in transferring ownership? I know PayPal has resources that would like to use this project in the future. |
|
@gabrielcsapo Would you be interested in helping me out with modserv instead? It's very much the continuation of |
|
@gabrielcsapo if you are happy with @wmhilton's fork, let me know. Otherwise I'm happy to grant either one of you or both of you maintainer privileges. |
|
@nolanlawson I would still like to maintain this source project, I think there is merit in both projects |
|
@gabrielcsapo Sorry for the late reply; I was taking a vacation from GitHub. You should now have full rights to this repo and to the npm package. Please do with it as you like! 😃 |
|
@nolanlawson you rock! Are you still open for discussion on the direction of the project? |
|
I'd rather just let you take the wheel. :) If you want to move it to a
GitHub org though, I think that may be a good first step so that my name
isn't attached to it anymore. That way it's clear that I'm not the "owner"
or BDFL or anything.
…-----
Nolan Lawson
http://nolanlawson.com
https://github.com/nolanlawson
On May 17, 2017 9:23 AM, "Gabriel Csapo" ***@***.***> wrote:
@nolanlawson <https://github.com/nolanlawson> you rock! Are you still
open for discussion on the direction of the project?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#122 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AARUwpaejbWJUGcorrQuOf-vs6b-5M7yks5r6x7pgaJpZM4Ie1bM>
.
|
|
Will move to my personal repo until I get more people to maintain a standalone organization, @nolanlawson does that sound reasonable? |
|
However you want to do it! :) Feel free to create a "local-npm" org,
though; I think it may be easier from the GitHub UI perspective, especially
if your repo is a fork of mine.
…-----
Nolan Lawson
http://nolanlawson.com
https://github.com/nolanlawson
On May 17, 2017 10:34 AM, "Gabriel Csapo" ***@***.***> wrote:
Will move to my personal repo until I get more people to maintain a
standalone organization, @nolanlawson <https://github.com/nolanlawson>
does that sound reasonable?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#122 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AARUwu0jI5yU4onLkbu7nGpHCSY5EZ52ks5r6y-0gaJpZM4Ie1bM>
.
|
|
@nolanlawson seems like I am unable to transfer it to anywhere :( |
|
I created https://github.com/local-npm @nolanlawson and added you as an owner. |
|
My bad, I will transfer.
…-----
Nolan Lawson
http://nolanlawson.com
https://github.com/nolanlawson
On May 17, 2017 11:46 AM, "Gabriel Csapo" ***@***.***> wrote:
I created https://github.com/local-npm @nolanlawson
<https://github.com/nolanlawson> and added you as an owner.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#122 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AARUwsG-uiXJoqGXQ24icxkdIP_8C8E2ks5r60COgaJpZM4Ie1bM>
.
|
|
OK, you are now an admin, forgot to give you those privileges before |
|
woot woot @nolanlawson thank you! |
|
OSS projects never truly die, they just become one with the Force. 😂 Such a beautiful peaceful transfer of power, I'm tearing up a little. |
|
I am hoping this project and yours @wmhilton will coalesce at one point or another! |
|
:) I am definitely happy to contribute to either!
That sounds promising! |
|
@wmhilton I am kind of the only resource right now :) |
|
@gabrielcsapo can you remind me what is your plan with this project? |
From now on, there will be this little badge in the local-npm README:
Also when you open new issues or PRs, the issue template will tell you it's unmaintained.
This project was fun and useful while it lasted. I've actually used it as my primary npm server on my personal MacBook for the past year. It works great.
local-npm started off as a proof-of-concept to show it was possible to easily build an npm server using PouchDB. Now it's accomplished that and a lot more.
However, the project is very ambitious, and it's currently consuming more of my time with issues, PRs, and questions than I'm reasonably able to manage. It needs work. In particular, it really ought to support private modules (#116),
npm publishought to get fixed (#118), and it should proactively download new tarballs (#102) for a truly offline experience.At this point, though, it offers minimal benefit over
--cache-min 99999999(as I learned recently from a talk by @seldo ; thanks for setting me straight), since that trick will also (AFAICT) avoid the metadata request, as local-npm does. Now, if local-npm actually proactively downloaded newly published tarballs as it listened to the changes feed, that would make it a slam dunk, but I really don't have time to work on that.Also, I fully expect the npm team to continue improving performance and the offline/lie-fi/slow-fi experience, so it's probably best just to put our weight behind their efforts. local-npm still stands as a useful tool for some cases (e.g. a workshop where everybody connects to one local-npm that already has the packages cached), but as a general purpose "offline npm" I don't think it makes much sense.
Thanks to everyone who filed issues and helped out, especially @calvinmetcalf who wrote a significant chunk of the daisy-chaining, tarball, and CLI logic. If anybody wants to take over this project, open up some PRs and I'll be happy to give you commit access. :)