Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Evaluate performance #5

Open
6 tasks
iandunn opened this issue Feb 2, 2021 · 0 comments
Open
6 tasks

Evaluate performance #5

iandunn opened this issue Feb 2, 2021 · 0 comments
Milestone

Comments

@iandunn
Copy link
Owner

iandunn commented Feb 2, 2021

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 iandunn added this to the MVP milestone Feb 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant