Skip to content

Commit

Permalink
Updated express to 2.4.3
Browse files Browse the repository at this point in the history
  • Loading branch information
tj committed Jul 22, 2011
1 parent c61c672 commit c501508
Show file tree
Hide file tree
Showing 2 changed files with 17 additions and 0 deletions.
1 change: 1 addition & 0 deletions .gitignore
@@ -1,3 +1,4 @@
*~ *~
\#*\# \#*\#
.\#* .\#*
node_modules
16 changes: 16 additions & 0 deletions package.json
@@ -0,0 +1,16 @@
{
"name": "browserid"
, "version": "0.0.1"
, "private": true
, "dependencies": {
"express": "2.4.3"
, "xml2js": "0.1.5"
, "sqlite": "1.0.3"
, "nodemailer": "0.1.18"
, "mustache": "0.3.1-dev"
, "cookie-sessions": "0.0.2"
, "vows": "0.5.8"
, "bcrypt": "0.2.3"
, "ejs": "0.4.3"
}
}

3 comments on commit c501508

@lloyd
Copy link

@lloyd lloyd commented on c501508 Jul 22, 2011

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

k, sorry for n00b questions, but what we should tell folks here is to run npm install after checkout to populate node_modules with the required dependencies?

Should run.js itself programatically hook npm to make sure deps are up to date?

@tj
Copy link
Owner Author

@tj tj commented on c501508 Jul 22, 2011

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yup npm install on changes to deps is fine. I've never personally done anything to ensure that they are up to date within the app itself, not sure what npm exposes for that

@tj
Copy link
Owner Author

@tj tj commented on c501508 Jul 22, 2011

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

weird though i just meant to change the one version and it added the whole file

Please sign in to comment.