After deployed today all icons where missing. My .npmignore looked like this (ignore *, explicitly un-ignore the files that shall be deployed):
In past this worked but now the images folder was not deployed (everything else was). I changed it to this (un-ignore everything in images folder):
npm pack still creates an archive that contains exactly what I specify (un-ignore).
So now also the development artifacts are deployed (Makefile, svg images and separate images that will be compiled into sprites.png). It's kinda ugly but doesn't really matter.4 votes
Allow to extend list of users who can maintain a package2 votes
My website ran out of memory, I need to have a tool that can restart it to release memory without manual intervention
Given I want 24/7 on website
And my resources on jitsu are only 256M,
And my website is is running out of memory for N reasons,
Then I need to have a tool that can restart it without manual intervention1 vote
Allow people to subscribe to a package and receive notifications when new versions are released.1 vote
Make native code compilation be something that nobody ever notices, because it never breaks. Also, it shouldn't write anything to the log unless it goes wrong.5 votes
This would allow much easier systems for automation, caching and experimentation. https://github.com/ForbesLindesay/npm-fetch is a long way along the way, but still needs an investment of time and energy.6 votes
All publish requests should still go to the public NPM, but all GET requests should be cached within the organisation so that only one person needs to get each resource from the public internet.3 votes
All of the packages in the public npm are also stored in Manta, making it relatively straight-forward to index them with a static-analysis tool like esprima.
We could do this for private packages as well without depending on Manta.
We could even expose this feature publicly!1 vote
Private modules are your applications and their own private dependencies. For those compliance in their organization they want to know what Open Source licenses they are depending on.1 vote
No notifications at all right now in the front-end at *.npm.nodejitsu.com. This would notify users on your team once and only once.1 vote
Right now you have to login with your npm username and password, which not everyone has since not everyone publishes modules.
Sign-in with Github would simplify this since it has a much larger user base.5 votes
There is only one team right now in a private npm registry. For this we would sync all your teams from Github.1 vote
- Don't see your idea?