thanks !
hxgdzyuyi
mcrumm
Phoenix Core Team
v0.5.0 (2022-04-28)
- Support upstream arm64 binaries
- Update Sass version to
1.49.11
A note about the Sass version
While there are newer releases of the dart-sass package available, v1.50.0+ currently has a broken --watch implementation and must not be used until it is fixed and a new version is released. Fortunately once that happens we should be able to remove the bash runner script from the Elixir package.
2
mcrumm
Phoenix Core Team
v0.5.1 (2022-08-26)
- Update Sass version to
1.54.5 - Skip platform check when given a custom path (h/t @jgelens)
- Use only TLS 1.2 on OTP versions less than 25.
2
mcrumm
Phoenix Core Team
v0.6.0 (2023-04-19)
Potentially breaking change: Due to a change in the upstream package structure, you must specify a :version >= 1.58.0 on Linux platforms.
1
tj0
PSA:
For those using SASS because of nesting and variables, esbuild might just be enough now. Using 0.17.18 atm.
By setting the target to be chrome58, it will rewrite the new css nesting rules to be functional on browsers that don’t support it. BEM won’t work anymore as the & operator no longer does a strict append in all cases. However, by using CSS variables, I got rid of SASS with a bit of rewriting.
The details
config.exs
config :esbuild,
version: "0.17.18",
default: [
args: ~w(js/app.js --bundle --target=es2016,chrome58 --outdir=../priv/static/assets --external:*.woff2 --external:*.svg),
cd: Path.expand("../assets", __DIR__),
env: %{"NODE_PATH" => Path.expand("../deps", __DIR__)}
]
app.js
App.js includes the css file for esbuild to generate and dump everything into priv/static/assets
import "../css/app.css"
1
mcrumm
Phoenix Core Team
v0.7.0 (2023-06-27)
This release should be fully compatible with Elixir v1.15+
- Require Elixir v1.11+
- Mark inets and ssl as optional apps
- Ensure the install task only loads the runtime config with
--runtime-config
0