A few weeks back i built a node like stack to run web apps in a
sandbox.
What this stack did was simulate the environment or location of the
app. So if my app.js file saved to “/home/stack/myapp/app.js” then
__dirname would be just “/” as in the root of the file system.
The problem you have it tha
What you're looking for is err.stack I think its a getter or the new
error object
On Feb 23, 9:56 am, GN wrote:
> I've just upgraded node from 0.4.12 to 0.6.11 and noticed that my JSON
> responses that used to have stack traces no longer include it. Am I
> possibly missing a parameter that needs
Oh never mind. Its not what you're looking for.
On Feb 23, 12:56 pm, TipTop wrote:
> What you're looking for is err.stack I think its a getter or the new
> error object
>
> On Feb 23, 9:56 am, GN wrote:
>
>
>
> > I've just upgraded node from
Yeah I should not have done it three time sorry.
To your problem you might want to call
Error.prototype.captuerStackTrace
On Feb 23, 12:56 pm, TipTop wrote:
> What you're looking for is err.stack I think its a getter or the new
> error object
>
> On Feb 23, 9:56 am, GN wrot
So I would like to know where node thinks it will be in 1 year?
What are things that are been looked at for improvement with node as a
whole?
At some point nodes going to run into a wall, and that wall is javascript.
I feel that js is nodes achilles heel. I LOVE js and live by it but its has
f
