We were discussing this with gl and we realized that the differences (like in the past.. ) between writing code that becomes an open source node module vs writing code that is part of a deployable (web service/web app or even executable) are even fewer.
In reality it seems to me that you always need to think that you "deploy" your code
0. npm version major to 1.0 from 0.xx
1. fix up the readme
2. add keywords to package.json to allow searches to find you
3. possibly add command line executables, man page in your npm
4. possibly add a drawing the way substack does
5. post the link/readme of the module to your blog/twiter
6. go through the places that you search to find a module (and when you didn'y you ended up builting it) and let them know you did (github issue comments, stack overflows, node mailing list
7. (there are probably sites that are have some "new/cool modules… where it may be worth to submit your module to…)
--
Of course when you are substack.. all you need to do is add the module as public repo and your followers all find it… but even then he still does the 1..5.
It is also interesting that you rarely have a module that doesn't have a natural deploy:
- gl created a random-password service. Its a deployable but ideally he should have captured the logic into a module - excluding the mouse-generating-randomness - the module's function would probably have a optional "randomness" paramterer.
- I created a slugify-url module... given that its use is to create mnemonic filenames out of urls... it makes sense as npm -g installed executable with a man page etc.
In reality it seems to me that you always need to think that you "deploy" your code
0. npm version major to 1.0 from 0.xx
1. fix up the readme
2. add keywords to package.json to allow searches to find you
3. possibly add command line executables, man page in your npm
4. possibly add a drawing the way substack does
5. post the link/readme of the module to your blog/twiter
6. go through the places that you search to find a module (and when you didn'y you ended up builting it) and let them know you did (github issue comments, stack overflows, node mailing list
7. (there are probably sites that are have some "new/cool modules… where it may be worth to submit your module to…)
--
Of course when you are substack.. all you need to do is add the module as public repo and your followers all find it… but even then he still does the 1..5.
It is also interesting that you rarely have a module that doesn't have a natural deploy:
- gl created a random-password service. Its a deployable but ideally he should have captured the logic into a module - excluding the mouse-generating-randomness - the module's function would probably have a optional "randomness" paramterer.
- I created a slugify-url module... given that its use is to create mnemonic filenames out of urls... it makes sense as npm -g installed executable with a man page etc.
Spin the wheel of the free casino slots machines and watch the jackpot magic happen! Playtika Rewards is free to hitch, and your membership is automatic! First and foremost, be aware of|concentrate on|pay consideration to} the sport version that you are playing in} and of the essential roulette wheel rules. Secondly, 카지노사이트 place your bets on the roulette table during the time window you could have}.
ReplyDelete