[josevalim]

I think the keyword in the v1.9 announcement was "major user-facing features". :) Back then we also said:

> We will continue shipping new releases every 6 months with enhancements, bug fixes and improvements.

I would say v1.10 is quite close to this sentiment: a bunch of improvements and enhancements but nothing really major. The main new feature in v1.10 is "compiler tracing" but that will be directly used by a small subset of the community, to improve the tooling, instead of being something everyone would use from the get go.

[alberth]

Jose

I really love the years of work you’ve put into Elixir (and Phoenix as a framework).

Can’t say thank you enough.

[josevalim]

Thank you, I appreciate it!

[jsmoov]

+1

[jacquesm]

Hello Jose, first of all, thank you for Elixer and Phoenix. A question that has been bugging me for a long time why Phoenix (arguably, built on one of the most reliable and battle tested stacks) has a dependency on NPM, something that I'd rather not see on any of my computers at all. Would you care to give insight into how this decision was reached and what if anything can be done to do Phoenix development and deploys without any NPM dependencies?

thank you!

[josevalim]

I believe there is a flag you can pass when you create your Phoenix application that removes webpack/npm/etc. If you are using Phoenix to build APIs, then you can pass `--no-html`, that will get rid of these and other dependencies. However, if you are writing JavaScript/CSS, than it is most likely that you want to use the tooling that exists in the Node ecosystem.

TL;DR - you can opt-out at any time.

[emerongi]

There is a --no-webpack flag