Yup. When I get the chance. Optionally also omit core and node_modules
lines in the long stack traces.
On Fri, Nov 16, 2012 at 12:40 AM, Alexey Kupershtokh <
alexey.kupersht...@gmail.com> wrote:
> Any plans on making the long traces optional like trycatch(cb, cb2, true)
> or probably configurabl
You'll have to disable caching and it will work, this saved would print the
directory that required the module;
delete require.cache[__filename];
module.exports = function() {
var path = require('path');
console.log(path.dirname(module.parent.filename));
};
On Saturday, Novemb
On Mon, Nov 12, 2012 at 3:22 AM, boden wrote:
> doesn't *have* to, but does for ease of use -- it defaults some paths
> relative to the caller's (the module require()ing) module location...
> obviously there are other approaches such as forcing the require()er to
> pass in those paths rather than
>
> Thanks - I need to heed my own advice - RTFM
--
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
Groups "nodejs" group.
To post to this group, send em
On Friday, November 16, 2012 6:58:42 PM UTC-6, Ben Noordhuis wrote:
>
> On Sat, Nov 17, 2012 at 1:08 AM, Ron Lambkin >
> wrote:
> > I am trying to install node.js on a DreamHost VPS. Upon doing ./config,
> I
> > get this error:
> > File "./configure", line 273
> > o['default_configura
