Use dive instead of findit to prevent issue

[pvorb]

There is an issue in findit/seq that causes nide to crash when loading a big project:

• https://github.com/substack/node-findit/issues/2
• https://github.com/substack/node-seq/issues/17

massimiliano-giroldi asked me, if dive could do the job. I looked at the code of seq and assumed the error got something to do with the chaining of seq.

So I patched nide. Now

• it uses dive
• it's faster
• issue does not occur anymore

Feel free to test it.

[coreh]

Wow man, thank you so much for this!

I tried it on a directory structure with thousands of files and hundreds of subdirectories, and the issue seems to be gone. Project loading also feels so much faster now. Thanks to you and @massimiliano-giroldi.

[pvorb]

NP. That was fun ;).

Cool project, by the way!

[max-giro]

nide & dive rocks together!

P.S.:
I think now there is a .nide dir (5.5MB) installed with the module (needs cleaning?).

[coreh]

oops. But that's strange. It's fixed now, but if you look at my .npmignore
file, .nide is there.

-- Marco Aurlio

On Thu, Sep 29, 2011 at 11:46 PM, massimiliano-giroldi <
reply@reply.github.com>wrote:

nide & dive rocks together!

P.S.:
I think now there is a .nide dir (5.5MB) installed with the module (needs
cleaning?).

Reply to this email directly or view it on GitHub:
#12 (comment)

[max-giro]

Reinstalei de novo e agora está mesmo sem a 'bagagem' toda : )