Phoenix 1.2.4
https://github.com/brunch/javascript-brunch
Also, the included brunch is over a year old.
Seams like you are using an outdated phoenix installer, since this was already fixed here: https://github.com/phoenixframework/phoenix/commit/6a7392ee7245e8266e67f3365ee8eab1050da8c0
"Seems?" Phoenix 1.2.4, which is from yesterday.
{
"repository": {},
"license": "MIT",
"scripts": {
"deploy": "brunch build --production",
"watch": "brunch watch --stdin"
},
"dependencies": {
"phoenix": "file:deps/phoenix",
"phoenix_html": "file:deps/phoenix_html"
},
"devDependencies": {
"babel-brunch": "~6.0.0",
"brunch": "2.7.4",
"clean-css-brunch": "~2.0.0",
"css-brunch": "~2.0.0",
"javascript-brunch": "~2.0.0",
"uglify-js-brunch": "~2.0.1"
}
}
Well, sorry for the gramma mistake.. Seems you are (like me) just starting with phoenix, I suggest to use the newer 1.3.0-rc installer
mix archive.install https://github.com/phoenixframework/archives/raw/master/phx_new.ez
Again, your assumptions are wrong. Not starting, using!
Look at the release. It contains the old file. https://github.com/phoenixframework/phoenix/blob/fbb8f6004615b1c71e03caf68871d056d3cc94e9/installer/templates/static/brunch/package.json
Unstable releases are unsupported and require too many, fragile changes that are subject to change... a non-starter.
However, should be a simple PR for a non-starter 馃憤
css-brunch is also deprecated.
@steakknife to be fair, @webdeb was just trying to be helpful and point your towards the new 1.3-rc installer which includes the latest brunch and would have fixed your issues. I know you're on an older stable version which is just fine. The v1.1/2 branches were using older brunch packages, but those have remained stable up until you just reported issues. We try to keep the churn on our js side to a minimum since folks run into issues even on seemingly stable point releases npm package wise. Thanks for the PRs, and remember to be kind :)
Most helpful comment
@steakknife to be fair, @webdeb was just trying to be helpful and point your towards the new 1.3-rc installer which includes the latest brunch and would have fixed your issues. I know you're on an older stable version which is just fine. The v1.1/2 branches were using older brunch packages, but those have remained stable up until you just reported issues. We try to keep the churn on our js side to a minimum since folks run into issues even on seemingly stable point releases npm package wise. Thanks for the PRs, and remember to be kind :)