Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7412359
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 29, 20262026-05-29T06:31:40+00:00 2026-05-29T06:31:40+00:00

Tonight I decided I’d try to build a simple Node.js application using Express on

  • 0

Tonight I decided I’d try to build a simple Node.js application using Express on my Windows 7 machine. The installation went fairly smoothly, but Express refuses to cooperate. Here are the steps I’ve taken:

  1. Installed Node.js using the MSI available at http://nodejs.org/dist/v0.6.9/node-v0.6.9.msi
  2. Installed Express by running npm install express g from a command prompt.
  3. Created a directory for the application c:\source\node> mkdir newapp.
  4. Changed directory to the application directory c:\source\node> cd newapp.
  5. Ran Express: c:\source\node\newapp> express --sessions --css stylus.

At this point the node.exe process fires up and runs endlessly at 25% CPU Time and continually uses more memory. After running for 20+ minutes the node.exe process uses 300+ MB of Memory. The express command never completes and the newapp directory remains unaltered.

If I run express --help I see the help output in the console. I’ve tried running the command prompt as and Administrator but still Express appears to hang.

Does anyone have a clue what’s going on or what I’m doing wrong? Thanks in advance!

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-29T06:31:41+00:00Added an answer on May 29, 2026 at 6:31 am

    This is a bug in the Windows version of Node v0.6.9. Filesystem access is pretty much messed up. Rollback to v0.6.8 http://nodejs.org/dist/v0.6.8/node-v0.6.8.msi and you should be fine.

    The Express.js command line on Windows doesn’t quite work well either. I just tried with Node v0.6.8.

    This works

    express --sessions myapp
    

    This doesn’t work for me

    express --sessions --css stylus myapp
    

    Fortunately you can add stylus support manually in your generated app. Open up app.js and in the app.configure function, add:

    app.use(require('stylus').middleware({src: __dirname + '/public'}));

    Hope this helps!

    Update:

    Oh ya, don’t forget your NPM commands. In your app directory, you may need to npm install jade and npm install stylus.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

While working a project tonight, I ended up using one .js resource file for
Third try at fixing this tonight - trying a different approach than before now.
I have encountered odd behavior when using document.getElementById tonight. Duplicated in Firefox 3 and
I just started using Selenium 2 tonight so this will be very basic (I
I'm teaching myself some Django tonight using the local dev package at instantdjango.com I
JQuery Mobile is making my cry tonight. I'm trying to build custom controls so
Tonight I copied an ASP 2.0 web site onto a client's machine, and lo!
I went to a .NET user group meeting tonight, and part of it revolved
I just started using QtCreator tonight, and it seems it puts all of the
So I decided to have some pointer fun tonight :) CursorHBList::CursorHBList(UINT iNumHB) :m_ppCursorHB(nullptr) ,m_iNumHB(iNumHB)

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.