Closed col closed 8 years ago
Should this set the npm version to the most recent too?
Yeah I think you're right. Bumping the node version was enough to fix my problem but they should be upgraded together. I'll update the pull request tonight.
On Monday, January 4, 2016, Chris McGrath notifications@github.com wrote:
Should this set the npm version to the most recent too?
— Reply to this email directly or view it on GitHub https://github.com/gjaldon/heroku-buildpack-phoenix-static/pull/14#issuecomment-168675025 .
Simply bumping the Node version doesn't seem to work for me when upgrading to Phoenix 1.1.2.
I have raised a separate issue https://github.com/gjaldon/heroku-buildpack-phoenix-static/issues/15.
Thanks for the PR @col!
This addresses an issue when trying to compile assets in when using Phoenix 1.1.0.
See https://github.com/phoenixframework/phoenix/issues/1410 for more details.