StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PODeploying Node.JS app to Heroku - Caching issues?
primarykey
Id
14759923
data
AcceptedAnswerId
14774022
AnswerCount
5
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-02-07T19:59:20.273
FavoriteCount
1
LastActivityDate
2017-12-16T09:45:58.203
LastEditDate
2013-02-08T12:04:31.667
LastEditorUserId
1058466
OwnerUserId
1058466
ParentId
0
PostTypeId
1
Score
1
ViewCount
1858
LastEditorDisplayName
text
Body
I'm currently trying to push my app to Heroku. I already been able to deploy it a few times, but now I've updated mongoose from ">= 3.5.0" to ">= 3.6.0rc0" in my packages.json file. However, version 3.6 requires mpath and mpromise. When the slug compilation begins, it uses a cached version of mongoose or something, as my when my application launches, I get "Error: Cannot find module 'mpath'". I trying to setup a custom buildpack Git that would stop the caching, I just commented out the cache stuff in bin/compile, available here: <a href="https://github.com/jValdron/heroku-buildpack-nodejs" rel="nofollow">https://github.com/jValdron/heroku-buildpack-nodejs</a> Here is an output of the push: <a href="http://pastebin.com/L3Yqy2NR" rel="nofollow">http://pastebin.com/L3Yqy2NR</a> Also, when I removed some dependencies from package.json, if I login with 'heroku run bash', I can see that those removed dependencies in node_modules. I already tried to remove the node_modules folder and do another 'git push', that didn't work either. And those removed deps are still in node_modules. Anyone have an idea on how to fix this? EDIT: Here is my package.json file: <pre><code>{ "name": "souply-api", "version": "0.1.0", "author": "Jason Valdron <jason.valdron@orangesprocket.com>", "description": "Main gears that runs the Soup.ly application", "dependencies": { "bcrypt": ">= 0.7.3", "express": ">= 3.0.5", "extend": ">= 1.1.3", "imagemagick": ">= 0.1.3", "jade": ">= 0.27.7", "knox": ">= 0.4.6", "less": ">= 1.3.1", "less-middleware": ">= 0.1.9", "moment": ">= 1.7.2", "mongoose": ">= 3.6.0rc0", "mongoose-types": ">= 1.0.3", "node-native-zip": ">= 1.1.0", "nodemailer": ">= 0.3.37", "oauth2orize": ">= 0.1.0", "passport": ">= 0.1.15", "passport-local": ">= 0.1.6", "passport-google": ">= 0.2.0", "passport-facebook": ">= 0.1.4", "passport-twitter": ">= 0.1.4", "passport-http": ">= 0.2.1", "passport-http-bearer": ">= 0.2.0", "passport-oauth2-client-password": ">= 0.1.0", "poor-form": ">= 1.1.3", "request": ">= 2.12.0", "socket.io": ">= 0.9.13" }, "engines": { "node": "0.8.x", "npm": "1.1.x" } } </code></pre> Mongoose is set as 3.6.0rc, as previously said. Mpath is a dependencies in Mongoose's package.json file. If I look at my local mongoose package.json file, I can see this: <pre><code>"dependencies": { "hooks": "0.2.1" , "mongodb": "1.2.11" , "ms": "0.1.0" , "sliced": "0.0.3" , "muri": "0.3.0" , "mpromise": "0.2.0" , "mpath": "0.1.1" } </code></pre> Also, if I login with <code>heroku run bash</code>, and navigate to <code>node_modules/mongoose/node_modules</code> I see that mpath and mpromise is not there.
Tags
<node.js><heroku><npm>
Title
Deploying Node.JS app to Heroku - Caching issues?
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USjValdron
UserOwnerUserId
1. USjValdron
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PODeploying Node.JS app to Heroku - Caching issues?
 UserUserId
 USBuu Nguyen
 VoteTypeVoteTypeId
 VTFavorite
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.