heroku-buildpack-meteor icon indicating copy to clipboard operation
heroku-buildpack-meteor copied to clipboard

/tmp/buildpack20160113-163-1jx5pre/bin/compile_meteor: line 66: cd: ../build/bundle/programs/server: No such file or directory

Open bloolizard opened this issue 9 years ago • 2 comments

Had been working until this morning. Not sure what happened.

Edwins-MacBook-Pro:dine_bella_vita edwizzle$ git push heroku master Counting objects: 5, done. Delta compression using up to 8 threads. Compressing objects: 100% (5/5), done. Writing objects: 100% (5/5), 420 bytes | 0 bytes/s, done. Total 5 (delta 4), reused 0 (delta 0) remote: Compressing source files... done. remote: Building source: remote: remote: -----> Fetching set buildpack https://github.com/jordansissel/heroku-buildpack-meteor.git... done remote: -----> meteor app detected remote: remote: -----> Moving app source into a subdirectory remote: remote: Node engine: 0.10.40 remote: Npm engine: unspecified remote: Start mechanism: none remote: node_modules source: none remote: node_modules cached: true remote: remote: NPM_CONFIG_PRODUCTION=true remote: NODE_MODULES_CACHE=true remote: remote: PRO TIP: Use 'npm init' and 'npm install --save' to define dependencies remote: See https://devcenter.heroku.com/articles/nodejs-support remote: remote: PRO TIP: Include a Procfile, package.json start script, or server.js file to start your app remote: See https://devcenter.heroku.com/articles/nodejs-support#runtime-behavior remote: remote: -----> Installing binaries remote: Downloading and installing node 0.10.40... remote: remote: -----> Building dependencies remote: Skipping dependencies (no source for node_modules) remote: remote: -----> Checking startup method remote: remote: -----> Finalizing build remote: Creating runtime environment remote: Exporting binary paths remote: Cleaning up build artifacts remote: Build successful! remote: /tmp/build_dbec11ec77a27c281c541350eda8aa51 remote: └── (empty) remote:
remote: remote: -----> Fetching Meteor 1.2.1 remote: Using cached Meteor 1.2.1 remote: remote: -----> Unpacking Meteor 1.2.1 remote: Meteor 1.2.1 is installed remote: remote: -----> Building Meteor App Bundle remote: Unable to update package catalog (are you offline?) remote:
remote: If you are using Meteor behind a proxy, set HTTP_PROXY and HTTPS_PROXY remote: environment variables or see this page for more details: remote: https://github.com/meteor/meteor/wiki/Using-Meteor-behind-a-prox remote:
remote: This project says that it uses Meteor 1.2.1, but you don't have that version of remote: Meteor installed, and we were unable to contact Meteor's update servers to find remote: out about it. Please edit the .meteor/release file in the project and change it remote: to a valid Meteor release, or go online. remote: remote: -----> Installing App's NPM Dependencies remote: /tmp/buildpack20160113-163-1jx5pre/bin/compile_meteor: line 66: cd: ../build/bundle/programs/server: No such file or directory remote: remote: ! Push rejected, failed to compile meteor app remote: remote: Verifying deploy... remote: remote: ! Push rejected to dinebellavita. remote: To https://git.heroku.com/dinebellavita.git

bloolizard avatar Jan 13 '16 18:01 bloolizard

You can try using a different buildpack, like this one: https://github.com/AdmitHub/meteor-buildpack-horse

I was having the same problem and switching build packs fixed it for me. I submitted a ticket to Heroku and the response I got was basically that this buildpack no longer works. They have been receiving many complaints from Meteor app developers who are using this same buildpack.

rfines avatar Jan 22 '16 19:01 rfines

@rfines That worked great, thanks for the help!

bloolizard avatar Jan 27 '16 18:01 bloolizard