If you often find yourself implementing complex logic and/or string
manipulation in your index.js file to load modules in your folder structure
in a fancy way you might this well-tested module helpful.
Check out the readme on GitHub for more info:
https://github.com/chakrit/xrequire
Also
HUB / MORE INFO
https://raw.github.com/chakrit/timer-shim
# NPM
$ npm install timer-shim --save
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Gro
dules (i.e. simple-acl) you might like this
module.
Full README is on GitHub as usual: https://github.com/chakrit/jam
If you have any suggestions/comments please don't hesitate to send it to me.
I really appreciate any/all feedbacks that you can give.
Thanks!
--
--
Job Board: http://jobs.
The use case is just to simplify arguments validation, which for me, is
getting repetitive and cumbersome in a project I'm currently building.
So I wrote the module.
Added an example.js
here: https://github.com/chakrit/have/blob/master/example.js if it'll helps.
On Sunday, March 17,
, 10, 20,
> 303, null, null, true); and so I would use 1 param options with default
> values, and in that case I want validation against each possible argument.
>
> On Mon, Mar 18, 2013 at 7:31 PM, chakrit
> > wrote:
>
>> The use case is just to simplify argument
of the arguments
> object. This is not guaranteed, as far as I know. This would cause your
> arguments to be matched against the wrong schemas.
>
> I'd suggest replacing the object input with an array input where order is
> guaranteed.
>
> On Sunday, 17 March 2013 05:23:29 UTC+1
;s probably not so good! You can replace it with this:
>
> return this._generator(size, function(e, buffer) {
> if (e) me.emit('error', e);
> else me.push(buffer);
> });
>
>
> On Mon, Apr 8, 2013 at 12:19 AM, Chakrit Wichian
> >
>
self-promotion: I think I might have built something on a similar
idea with https://github.com/chakrit/jam
that async calls should be treated as a highest-level thing and then
methods provided to join / fit them together.
might worth checking out :p
One big glaring caveat with pipeworks t
npm: npm install icu-wordsplit
GitHub repo: https://github.com/chakrit/node-icu-wordsplit
Readme: https://github.com/chakrit/node-icu-wordsplit/blob/master/README.md
This exports a function that splits a string up into an array of words
for the specified locale, for example:
var results
See this issue here: https://github.com/mikeal/request/issues/313
In short: `npm install request@2.11.0` does not install the module
properly and thus cause any depended module not install properly as well
I'm using resourceful and cradle in particular. This is possibly because of
the use of bu
Couldn't find one clean and simple ACL implementation. So I decided to
write one.
Github: https://github.com/chakrit/simple-acl
NPM: https://npmjs.org/package/simple-acl
Very alpha atm. but it's pretty simple and it has tests :)
Comments, patches and suggestions, pretty please? :
e:
>
> Have you seen mongoose-acl? Does it operate similarly to yours? It's nice
> and I've been using it for about 24 hours.
>
> -- Joshua Gross
> Christian / SpanDeX.io / BA Candidate of Computer Science, UW-Madison 2013
> 414-377-1041
>
> On Sep 5, 2012, at 2:0
npm install fts
GITHUB: https://github.com/chakrit/fts
NPM: https://npmjs.org/package/fts
NODE-FTS is a full-text-search engine that tries to be:
- fast - using pre-filled redis zsets, searching is one ZREVRANGE command
- fuzzy - using some basic pre-computation
- unicode - using
Underscore and lodash already does pretty much of what you will ever want.
I'd say keep the core small and use your _ for whatever's extra util you
need.
FWIW there is also https://github.com/chakrit/node-uneval so
`eval(uneval(o))` might work for you (also handles functions).
Of c
A. YES
B. NO
C. YES
D. NO
E. YES
On Friday, May 31, 2013 2:52:47 AM UTC+7, Dominic wrote:
>
> without looking in the documentation or trying it in the repl
>
> what do you expect to be the results of these tests on semver ranges?
>
> A. semver.satisfies('~1.2.3', '1.2.4')
>
> B. semver.satisfie
Meaning:
A: Around this version, so get the most recent version that's still not too
far from 1.2
B: 1.3 might have API changes, don't want it. I have programmed against 1.2
so let's stick to that for the moment
C: Around this version, like A
D: 1.2 with whatever patch version's available but no
Just hack this up in a pinch: https://npmjs.org/package/down
It keeps polling the github (and harvest and TODO:other services) and
prints green/red UP/DOWN messages.
Very useful to left running on the one of your tmux's pane for that moment
when you are waiting to `npm install` from a git repo
> It goes against the grain of everything node is.
I'm gonna second that. And besides, I imagine it shouldn't that hard
to roll a thin sync interface over the node core APIs using something
like fibers (https://github.com/laverdet/node-fibers)
On Apr 2, 10:00 am, Mark Hahn wrote:
> > I think i
: 'string or number'
, options : 'optional object'
, callback : 'function'
});
}
Basically a very short and concise DSL for validating arguments.
Install with `npm install have --save`
Head over to https://github.com/chakrit/have to check the R
Wrote this to test actual HTTP download speed.
Thought this might be useful to some as a generic testing tool.
Check out the README on GitHub if you are interested:
https://github.com/chakrit/randstream
Also provides a `rand` command line for generating random bytes in the shell if
installed
20 matches
Mail list logo
