-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Fails to deploy to Heroku #821
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Did you see this similar issue #530 ? |
@curvo I did, but I couldn't make anything out of it. Also, I don't us ts. |
I tried to run locally |
I also tried with webpack update to 3.0 and to master.... and result always the same. |
@AndreiMotinga comparing that to my deployment logs, right below the line where it says
my logs follow with
Can you verify that:
"engines": {
"node": ">=6.0.0",
"yarn": ">=0.25.2"
} |
@janklimo, thank you for the comment.
After adding it, here's the log
... in /app/javascript/packs/dropzone.js replaced and all went well. Once again, I appreciate the help. |
@AndreiMotinga Did you mean to close this? I am confused by your logs... did @janklimo's suggestions help you? |
@curvo I did.
It's a bit odd since I was able to compile locally using production env variables, but still. |
@AndreiMotinga Interesting. Sounds like the newer |
@janklimo
as you suggested, it gave me a log to go of. So... yeah, I guess, that's right. Thanks again. As to the root of the 'bug', why didn't it fail properly from the start - I don't know. |
I came across the same issue, after specifying the You must have Your {
"buildpacks": [
{ "url": "heroku/nodejs" },
{ "url": "heroku/ruby" }
]
} |
I had the same issue with vue. Using buildpack nodejs and then ruby (in that order) fixed the problem. Thank you @janklimo |
@AnwarShah Does adding both buildpacks duplicates |
Rails 5.1
webpacker 2.0
The text was updated successfully, but these errors were encountered: