-
Notifications
You must be signed in to change notification settings - Fork 4
Description
elm-tooling works, is fast and does what I need!
These days, the elm, elm-format and elm-test-rs npm packages are as tiny and secure as possible, which makes elm-tooling less relevant. (Only elm-json is left (zwilias/elm-json#51), but I’ve released @lydell/elm-json as a workaround). On top of that, pnpm lets you install npm packages with a global store similar to ~/.elm, making elm-format bring even less to the table. (This makes #22 not so important anymore.)
I would be fun to eventually implement #88. And it would be cool if elm-tooling was written in a language where you can create a small standalone binary, removing the dependency on Node.js and npm. But I’d rather focus on elm-watch and elm-safe-virtual-dom.
I’ll continue maintaining the project, and adding new tool versions as they are released, but no new features will be added.
That being said, elm-tooling isn’t going away anytime soon. But I think it’s healthy to actively re-evaluate the “reasons to exist” of a tool, even though it’s the baby you’ve created yourself!