That looks like a compile error. What does the stack trace look like? I
doubt the error is coming from server.js
On Tuesday, August 7, 2012 12:39:28 PM UTC-7, yishayw wrote:
>
> Hi,
>
> I have a site which uses a library with a static file named server.js.
> Node.js seems to be treating this as
Hello Roly,
To answer your question the stack trace looks like this:
===
C:\Users\Yishay\Documents\My Web Sites\Express Site\public\Server.js:1
alert('serving')
^
ReferenceError: alert is not defined
at Object. (C:\Users\Yishay\Documents\My Web Sites\Express
Site\public\Server.js:1:
I figure it out, the solution was in my IIS configuration. I changed
web.config so that all occurrences of 'server.js' were replaced with
'nodejs_server.js'. I then renamed all my node.js server files to
nodejs_server.js. Now my statically served library namespace doesn't
conflict with the node
Why use IIS with node?
You sacrifice everything, for what?
On 08/08/2012 11:38 AM, yishayw wrote:
I figure it out, the solution was in my IIS configuration. I changed
web.config so that all occurrences of 'server.js' were replaced with
'nodejs_server.js'. I then renamed all my node.js server fi
