Hello there.
I've created a new app using starter template, it's almost empty, works fine on local machine and gives me this error on heroku:

I have another nuxt app there, with older nuxt version and it works as intended, so I don't know what it could be.
Adding package.json, maybe it helps.
"name": "<>",
"version": "1.0.0",
"description": "<>",
"author": "<>",
"private": true,
"dependencies": {
"css-loader": "^0.27.3",
"firebase": "^3.7.3",
"nuxt": "latest",
"vue": "^2.2.6"
},
"scripts": {
"dev": "nuxt",
"build": "nuxt build",
"start": "nuxt start",
"generate": "nuxt generate",
"lint": "",
"precommit": "npm run lint",
"heroku-postbuild": "npm run build"
},
"devDependencies": {
"node-sass": "^4.5.0",
"sass-loader": "^6.0.2",
"webpack": "^2.2.1"
}
I'm seeing the same issue here. It worked fine with v0.9.x but since updating to v0.10.0 I've been getting this as well.
Don't want to be an asshole here, but since I could not do anything about this bug in my project, i've put it to some test.
I've deployed empty application to heroku. The only change I did was adding "heroku-postbuild": "npm run build" line to package.json and gitignoring .idea folder.
ENV vars are ofcourse set as intended:
src="https://cloud.githubusercontent.com/assets/16022609/24456262/288b11ac-149b-11e7-82e3-6ad9d08d36b4.png">
Repo which I deployed to double-check is here.
Sadly, this error persirst even with blank app. :( Thats why I suspect this might be an issue with nuxt or its dependencies itself, though I don't have any ideas how could I help fixing it without diving into nuxt core :(.
Hope this helps.
I can confirm 0.10.5 can't be deployed to heroku with empty nuxt/starter template .
I tried it today , and got same error .
deploy console have show some dependence warning/error , but I lost that information .
馃憢 Hey all, I believe this is actually a duplicate of #462. The workaround in that thread worked for me on Heroku. Best of luck!
@paulstraw Yup, that worked for me too, thanks.
Hope it gets fixed by default in future releases.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Most helpful comment
馃憢 Hey all, I believe this is actually a duplicate of #462. The workaround in that thread worked for me on Heroku. Best of luck!