perf

Open
#4 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
performance

Research direction

The issue names file-size limits/display and parse/eval-time measurements but no files or existing test to run. Start by locating the ember-new experiment entry points and any current performance checks; done would require agreed metrics and a repeatable regression test, but the remaining “??” leaves the scope unresolved.

Written by the indexing model from the issue text.

Description

  • file size limits/display
  • parse/eval time numbers (and test that we can run to update and ensure we don't regress)
  • ??
Dominant language
JavaScript
Stars
9
Forks
0
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ember-cli/ember-next

All issues in ember-cli/ember-next

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.