no-build-tools-no-problems icon indicating copy to clipboard operation
no-build-tools-no-problems copied to clipboard

Evaluate performance

Open iandunn opened this issue 4 years ago • 0 comments

How does this compare to the traditional approach? Is it good enough for small-medium projects?

  • [ ] Look for any perf bottlenecks, missing best practices, etc. Probably best to do this first, before comparing to traditional approach, in case matters.
  • [ ] Compare source/ + jspm.dev to traditional approach on the same code. Is it close enough that to justify eschewing tooling for the improved devex?
  • [ ] Compare build/ (with just source/ processed by Babel to remove HTM, etc) + jspm.dev to traditional approach on the same code. Is it close enough that to justify eschewing tooling for the improved devex?
  • [ ] Does the lack of tree shaking with jspm.dev introduce too much overlap in sub-dependencies?
  • [ ] Should preload be used instead of modulepreload?
  • [ ] Are there places we could use dynamic imports to speed up the initial load? (probably the latests post card)

iandunn avatar Feb 02 '21 15:02 iandunn