Heroku deploy problem

I have manage to solve WARNING: no package.json detected in root nor custom directory by adding assets_path="." instead of phoenix_relative_path but no joy I’m still having problems with not been able to deploy the app properly, I don’t understand why he can’t see deps folder

Can you try the following
in phoenix_static_buildpack.config, set node version above 8 (i got errors on node modules for lesser versions)
or set node_version=10.15.0

ok so changing node version helped but now this

remote:        * MIX_ENV=prod
remote:
remote: -----> Installing binaries
remote:        clean_cache option set to true.
remote:        Cleaning out cache contents
remote: Resolving node version 10.15.0...
remote: Downloading and installing node 10.15.0...
remote:        Installing Node 10.15.0...
remote:        Using default npm version
remote:
remote: -----> Building dependencies
remote:        Installing and caching node modules
remote: npm WARN assets No description
remote:
remote:        up to date in 0.45s
remote:        found 0 vulnerabilities
remote:
remote:        npm WARN deprecated babel-preset-es2015@6.24.1: 🙌  Thanks for using Babel: we recommend using babel-preset-env now: please read https://babeljs.io/env to update!
remote:        npm WARN deprecated nomnom@1.8.1: Package no longer supported. Contact support@npmjs.com for more info.
remote:        npm WARN deprecated browserslist@1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
remote:        npm WARN deprecated core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
remote:        npm ERR! code ENOLOCAL
remote:        npm ERR! Could not install from "../deps/phoenix" as it does not contain a package.json file.
remote:
remote:        npm ERR! A complete log of this run can be found in:
remote:        npm ERR!     /app/.npm/_logs/2019-12-29T07_33_56_086Z-debug.log
remote:  !     Push rejected, failed to compile Phoenix app.
remote:
remote:  !     Push failed
remote: Verifying deploy...```

this is a nightmare :cry:

hmm ok, now thats a path issue.
Thought of two things,

1. With node 10.15, Incase if you dont have asset_path in phoenix_static_buildpack, add it (assets_path=.) and update always_rebuild=true in elixir_buildpack.config.
   2.If that didn’t work, can you try reverting back to old version (node 6.9.2) and try the same.

so in my phoenix_static_buildpack I have defined

assets_path=.
clean_cache=true
node_version=10.18.0
npm_version=6.13.4

and in elixir_buildpack.config I have defined

always_rebuild=true
elixir_version=1.8.2
erlang_version=21.2.5

reverting back to old version did not solve the problem, I would really love if elixir didn’t use npm but yarn.

anyluck with the node 10.15, with the same settings? or the same error persist?

it’s the same.

Enumerating objects: 326, done.
Counting objects: 100% (326/326), done.
Delta compression using up to 12 threads
Compressing objects: 100% (224/224), done.
Writing objects: 100% (326/326), 190.93 KiB | 9.09 MiB/s, done.
Total 326 (delta 139), reused 202 (delta 79)
remote: Compressing source files... done.
remote: Building source:
remote:
remote: -----> Phoenix app detected
remote:
remote: -----> Loading configuration and environment
remote:        Loading config...
remote:        Detecting assets directory
remote:        * package.json found in custom directory
remote:        Will use phoenix configuration:
remote:        * assets path ./assets
remote:        * mix tasks namespace phoenix
remote:        Will use the following versions:
remote:        * Node 10.18.0
remote:        Will export the following config vars:
remote: DATABASE_URL
remote: NODE_MODULES_CACHE
remote: POOL_SIZE
remote: SECRET_KEY_BASE
remote:        * MIX_ENV=prod
remote:
remote: -----> Installing binaries
remote:        clean_cache option set to true.
remote:        Cleaning out cache contents
remote: Resolving node version 10.18.0...
remote: Downloading and installing node 10.18.0...
remote:        Installing Node 10.18.0...
remote:        Using default npm version
remote:
remote: -----> Building dependencies
remote:        Installing and caching node modules
remote: npm WARN . No description
remote:
remote:        up to date in 0.336s
remote:        found 0 vulnerabilities
remote:
remote:        npm WARN deprecated babel-preset-es2015@6.24.1: 🙌  Thanks for using Babel: we recommend using babel-preset-env now: please read https://babeljs.io/env to update!
remote:        npm WARN deprecated nomnom@1.8.1: Package no longer supported. Contact support@npmjs.com for more info.
remote:        npm WARN deprecated core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
remote:        npm WARN deprecated browserslist@1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
remote:        npm ERR! code ENOLOCAL
remote:        npm ERR! Could not install from "../deps/phoenix" as it does not contain a package.json file.
remote:
remote:        npm ERR! A complete log of this run can be found in:
remote:        npm ERR!     /app/.npm/_logs/2019-12-29T08_10_45_268Z-debug.log
remote:  !     Push rejected, failed to compile Phoenix app.
remote:
remote:  !     Push failed
remote: Verifying deploy...

why should I ever change the deps path, I don’t get it, I have spent four hours on this.

Hey found a similar thread in elixirforum, please check and try this

And this one as well
https://github.com/gigalixir/gigalixir-getting-started/issues/8#issuecomment-529055892

OMG, I didn’t set the elixir build pack so I was not building it properly, thanks @tenzil I need to go and chill a bit

After I did heroku create --buildpack hashnuke/elixir I forgot to heroku buildpacks:set hashnuke/elixir, and that was it, people read the documentation

you can easily use yarn, or parcel - or whatever is the latest and greatest..

I use yarn on heroku - I just have a yarn deploy in my compile file - which of course calls the deploy script in package.json..

  "scripts": {
    "deploy": "NODE_ENV=production webpack --mode production",