Open Collective
Open Collective
Loading
v2.1.0 Fix Build page and start using Ember
Published on April 17, 2020 by Ilya Radchenko

It has been a long time coming but Angular v1 has been really holding us back, with v2.1.0 the build page uses Ember, a framework known for longevity, community and lts releases.


Due to issues somewhere deep in the Angular chain, the job/build page stopped working. The Angular part of this project has been holding me back mainly due to its non SPA like architecture and how unsupported it is, I've started rewriting the build page in EmberJS. Ember is known for longevity and its lts policy. It's also focused on ambitious apps, which strider is. See issues #1076, #1082, #1083, etc for the issue.


The ember version uses typescript and tailwind, both upgrades. This allows us to remove jQuery and other old bootstrap dependency. Currently this upgrade just handles a few routes and you can see these have `?ember=true` in the url. This quirk will eventually go away, at the moment I use it to know which version to serve.


I'm not removing any old assets yet, since not everything is 100% feature complete, but at least the basics work for builds.


The goal is to remove angular 100% and rewrite APIs on the backend as we use them in the app. But those will come piecemeal as smaller PRs.