You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
The text was updated successfully, but these errors were encountered:
How does this compare to the traditional approach? Is it good enough for small-medium projects?
source/
+jspm.dev
to traditional approach on the same code. Is it close enough that to justify eschewing tooling for the improved devex?build/
(with justsource/
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?jspm.dev
introduce too much overlap in sub-dependencies?preload
be used instead ofmodulepreload
?The text was updated successfully, but these errors were encountered: