Hello
I was looking for something CoffeeScript-like but with a lispy source
language to play with (and likely contribute to), so was thrilled to find
Sibilant.
* * *
When I installed node (v 0.40), npm & sibilant per the instructions and
tried to run the repl I got an error along the lines of
> sibilant
node.js:116
throw e; // process.nextTick error, or 'error' event on first tick
^
Error: Cannot find module 'sibilant/cli'
at Function._resolveFilename (module.js:289:11)
at Function._load (module.js:241:25)
at require (module.js:317:19)
[snipsky]
I got past this by copying the contents of sibilant/lib into the main
sibilant directory, but that's clearly a messy fix.
Could there be something wrong with my set-up, that it's not searching /lib?
Thanks
Dan
Hi! What version of npm are you using? My guess is that this is a manifestation of a recent change Isaac made to npm that no longer uses the "modules" component of package.json. If that's the case, I'll have a fix for you in short order. Thanks for the bug report! –Jacob On Sun, Feb 20, 2011 at 3:56 PM, Daniel Prager <daniel.a.prager@gmail.com> wrote: > Hello > > I was looking for something CoffeeScript-like but with a lispy source > language to play with (and likely contribute to), so was thrilled to find > Sibilant. > > * * * > > When I installed node (v 0.40), npm & sibilant per the instructions and > tried to run the repl I got an error along the lines of > >> sibilant > > node.js:116 > throw e; // process.nextTick error, or 'error' event on first tick > ^ > Error: Cannot find module 'sibilant/cli' > at Function._resolveFilename (module.js:289:11) > at Function._load (module.js:241:25) > at require (module.js:317:19) > [snipsky] > > I got past this by copying the contents of sibilant/lib into the main > sibilant directory, but that's clearly a messy fix. > > Could there be something wrong with my set-up, that it's not searching /lib? > > > Thanks > > Dan > > > >
I'm getting the same error. npm 0.3.1 Ben On Sun, Feb 20, 2011 at 5:00 PM, Jacob Rothstein <jacob.rothstein@gmail.com>wrote: > Hi! What version of npm are you using? > > My guess is that this is a manifestation of a recent change Isaac made > to npm that no longer uses the "modules" component of package.json. > If that's the case, I'll have a fix for you in short order. > > Thanks for the bug report! > –Jacob > > On Sun, Feb 20, 2011 at 3:56 PM, Daniel Prager > <daniel.a.prager@gmail.com> wrote: > > Hello > > > > I was looking for something CoffeeScript-like but with a lispy source > > language to play with (and likely contribute to), so was thrilled to find > > Sibilant. > > > > * * * > > > > When I installed node (v 0.40), npm & sibilant per the instructions and > > tried to run the repl I got an error along the lines of > > > >> sibilant > > > > node.js:116 > > throw e; // process.nextTick error, or 'error' event on first > tick > > ^ > > Error: Cannot find module 'sibilant/cli' > > at Function._resolveFilename (module.js:289:11) > > at Function._load (module.js:241:25) > > at require (module.js:317:19) > > [snipsky] > > > > I got past this by copying the contents of sibilant/lib into the main > > sibilant directory, but that's clearly a messy fix. > > > > Could there be something wrong with my set-up, that it's not searching > /lib? > > > > > > Thanks > > > > Dan > > > > > > > > >
Ok, you should be able to `npm install sibilant` — I just pushed version 0.1.1, which works with the change to npm's modules. The fix was to (require "sibilant/lib/something") instead of (require "sibilant/something"). Thanks again for letting me know, –Jacob On Sun, Feb 20, 2011 at 4:01 PM, Ben Atkin <ben@benatkin.com> wrote: > I'm getting the same error. npm 0.3.1 > Ben > > On Sun, Feb 20, 2011 at 5:00 PM, Jacob Rothstein <jacob.rothstein@gmail.com> > wrote: >> >> Hi! What version of npm are you using? >> >> My guess is that this is a manifestation of a recent change Isaac made >> to npm that no longer uses the "modules" component of package.json. >> If that's the case, I'll have a fix for you in short order. >> >> Thanks for the bug report! >> –Jacob >> >> On Sun, Feb 20, 2011 at 3:56 PM, Daniel Prager >> <daniel.a.prager@gmail.com> wrote: >> > Hello >> > >> > I was looking for something CoffeeScript-like but with a lispy source >> > language to play with (and likely contribute to), so was thrilled to >> > find >> > Sibilant. >> > >> > * * * >> > >> > When I installed node (v 0.40), npm & sibilant per the instructions and >> > tried to run the repl I got an error along the lines of >> > >> >> sibilant >> > >> > node.js:116 >> > throw e; // process.nextTick error, or 'error' event on first >> > tick >> > ^ >> > Error: Cannot find module 'sibilant/cli' >> > at Function._resolveFilename (module.js:289:11) >> > at Function._load (module.js:241:25) >> > at require (module.js:317:19) >> > [snipsky] >> > >> > I got past this by copying the contents of sibilant/lib into the main >> > sibilant directory, but that's clearly a messy fix. >> > >> > Could there be something wrong with my set-up, that it's not searching >> > /lib? >> > >> > >> > Thanks >> > >> > Dan >> > >> > >> > >> > > >
Thanks Jacob Works a charm. -- Dan On Mon, Feb 21, 2011 at 11:17 AM, Jacob Rothstein <jacob.rothstein@gmail.com > wrote: > Ok, you should be able to `npm install sibilant` — I just pushed > version 0.1.1, which works with the change to npm's modules. The fix > was to (require "sibilant/lib/something") instead of (require > "sibilant/something"). > > Thanks again for letting me know, > > –Jacob > > On Sun, Feb 20, 2011 at 4:01 PM, Ben Atkin <ben@benatkin.com> wrote: > > I'm getting the same error. npm 0.3.1 > > Ben > > > > On Sun, Feb 20, 2011 at 5:00 PM, Jacob Rothstein < > jacob.rothstein@gmail.com> > > wrote: > >> > >> Hi! What version of npm are you using? > >> > >> My guess is that this is a manifestation of a recent change Isaac made > >> to npm that no longer uses the "modules" component of package.json. > >> If that's the case, I'll have a fix for you in short order. > >> > >> Thanks for the bug report! > >> –Jacob > >> > >> On Sun, Feb 20, 2011 at 3:56 PM, Daniel Prager > >> <daniel.a.prager@gmail.com> wrote: > >> > Hello > >> > > >> > I was looking for something CoffeeScript-like but with a lispy source > >> > language to play with (and likely contribute to), so was thrilled to > >> > find > >> > Sibilant. > >> > > >> > * * * > >> > > >> > When I installed node (v 0.40), npm & sibilant per the instructions > and > >> > tried to run the repl I got an error along the lines of > >> > > >> >> sibilant > >> > > >> > node.js:116 > >> > throw e; // process.nextTick error, or 'error' event on first > >> > tick > >> > ^ > >> > Error: Cannot find module 'sibilant/cli' > >> > at Function._resolveFilename (module.js:289:11) > >> > at Function._load (module.js:241:25) > >> > at require (module.js:317:19) > >> > [snipsky] > >> > > >> > I got past this by copying the contents of sibilant/lib into the main > >> > sibilant directory, but that's clearly a messy fix. > >> > > >> > Could there be something wrong with my set-up, that it's not searching > >> > /lib? > >> > > >> > > >> > Thanks > >> > > >> > Dan > >> > > >> > > >> > > >> > > > > > >