3: - for CJS, what kind of tree shaking is required (or is it ok to pull in the entire package) - how acceptable is it to end up with a lot of package duplicates? Is it tolerable? Would it be important to at least provide a warning? Does yarn --flat work?
-
-
It was more the design choice of only consuming es modules, etc. A consideration.
-
Ah. I'm quite, quite sure that the people on this thread would reject that solution (at least based on the plain wording of their requests). But maybe it'll change over time.
-
Getting an RFC started. When the PR lands, feel free to edit the shit out of it.
-
An RFC would be delightful. Probably read the packager RFC to see if there's anything worth cannibalizing, but I think a good RFC on this topic would be more focused on the above (and related) questions and less on implementation.
-
I need to get off the computer for a bit. Close if not so useful. No bad feelings here.
-
Yehuda it sounds like much of this could be accomplished in a vue-cli glimmer-cli approach. Making modules the and an elegant code splitting story _the ember convention_ seems like a powerful message too.
-
Something that other fws lack is a set of super svelte super modular answers to all the ember add-ons people would want (toolkits, libs, forms, etc). But none exist as esm libs all opinionated. That with a good code splitting story (and _a bundler_) seem like it answers "fatigue"
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.