@EndangeredMassa wrote:
I’m starting a brand new ember app for the first time in forever. I’m a huge fan of starting with guardrails in place for things that will be harder to add later, but easy to always follow along from beginning. I have a list of things I want to add right away, almost all of which I’ve used in the past:
- ember-a11y-testing
- ember-animated
- ember-cli-dependency-lint
- ember-cli-tailwind
- ember-concurrency
- ember-concurrency-decorators
- ember-intl
- ember-metrics
- ember-percy
- ember-simple-auth
- ember-template-lint (turn most rules on)
- ember-test-selectors
- ember-truth-helpers
- (maybe) corber
- (maybe) fastboot
I also would love to have some measure of performance testing automated from the beginning. I looked into scripting Ligthhouse to test this, which I can get to work, but it keeps reporting 15 seconds for Time to First Meaningful Paint on a brand new ember app, which doesn’t make any sense. Maybe I have something set up incorrectly.
I have some questions:
Does anyone do automated performance testing for the Ember apps? I’m thinking about payload size and time to first meaningful paint, but what other metrics are there that you like to automatically track regressions for?
What other “from the beginning” things would you add to a new ember app? I don’t think the type of application overly matters. I’d love to hear about whatever this questions means to you.
Posts: 1
Participants: 1
