‘Yarn add package’ ‘Import package from “package”’ Without any other ceremony.
-
-
Having spent equal time with ember addons and webpack configs, I like this in-between approach tbh. Tell me, the add-on author (in this case) what I need to target in order to hook into the rest of the Ember CLI build step and I’ll hit it
-
Yeah it might be a good starting point. If you provide loose ES modules without experimental features and opt in, it'll just work without additional shenanigans
-
That said, this does seem more like a solution for Ember addons rather than NPM packages that don’t know about ember to begin with. How do we get random 3rd party npm packages to “loose ES module” in a consistent way?
-
Something like the modules key might work. But now you're starting to see the problem. I think we can go with something like "CJS modules export a single default export and have very specific/lossy tree shaking semantics" to make existing modules work.
-
It just doesn't turn out that there's a very trivial transformation, and even just looking at what browserify and webpack has done, there's been a lot of small iterations over the years that affect apps in very noticeable ways. Time for someone to write an RFC!
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.
.