How to configure Webpack with Phoenix 1.4.0~

Phoenix Forum Questions / Help
, ,
1

I am learning with elixir: 1.9.1 and Phoenix: 1.4.9.
Phoenix: 1.4.0 ~ recognizes that the front build tool has changed from Brunch to Webpack.
However, brunch-config.js is still in the file generated by phoenix new.
There is something I want to check here.

What you want to check

Will you still use brunch-config.js? For example, when installing sass-brunch with 1.3.0, it seems that the setting is written to npm install-> brunch-config.js, but after 1.4.0, brunch-config.js should not be used basically. Is not it?
2. According to How to use SASS / SCSS with Webpack in Phoenix 1.4,
It is written that the setting is written in assets / webpack.config.js, but there is no such file in the generated file. Will this be created by yourself if necessary?

Thanks.

reference

How to use SASS / SCSS with Webpack in Phoenix 1.4

Phoenix 1.3 to 1.4-Migrating from Brunch to Webpack

2

You’re using an old version of phx_new, which is why you get the old template.

Use mix archive.install hex phx_new to upgrade to the latest version of the generator, and then try mix phx.new again, you shouldn’t get any brunch files.

2 Likes
3

Thank you for reply.
I thought I use mix archive.install hex phx_new on Docker…

  • Dockerfile
FROM elixir:1.9.1

RUN curl -sL https://deb.nodesource.com/setup_10.x | bash \
  && apt-get install -y nodejs

RUN npm install npm@latest -g

RUN mix local.hex --force && \
  mix archive.install hex phx_new 1.4.9 --force && \
  mix local.rebar --force && \
  mix archive.install https://github.com/phoenixframework/archives/raw/master/phx_new.ez --force

RUN apt-get install -y inotify-tools

WORKDIR /app
  • command
$ docker-compose run web mix phoenix.new APPNAME
4

Do not use phoenix.new its a legacy task and will eventually be removed. Please use phx.new.

3 Likes
5

I’m sorry for the mistake.
The problem was solved.
Thank you for your supports.