-
Notifications
You must be signed in to change notification settings - Fork 2
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
Which Loader should be used? #6
Comments
I think we need to define the set of requirements the loader should have so we can take a decision. Historically the design goals of liferay-amd-loader for
Later additions were:
What would you say is missing so we could use it? Do you see a way for us to implement what's missing in |
Fast review.
Notes
|
Also a great read for everyone on the topic is this discussion on System.js, systemjs/systemjs#1522. |
But the main reason to write a custom loader is #4. |
Throwing FuseBox into the mix as well 😉 |
I'll add pundle and assetgraph to the list |
This experimental implementation uses SystemJS to resolve, load, execute and cache modules.
I personally don’t believe in the final product SystemJS should be used.
Let me state my rationale.
Doesn‘t support pre-emptive modules’ dependencies knowledge (and parses files at runtime!).On the other side there are some good parts that would be very sad to loose. In particular:
Update — SystemJS does support pre-emptive module dependencies through a specific configuration:
meta: { 'a-pkg': { deps: [] } }
Update 2017/01/09 — references to issues and to System.js plugins.
The text was updated successfully, but these errors were encountered: