Having built a bunch of Ember apps with GraphQL, I think the biggest difficulty has been integrating libraries like apollo-client and related packages seamlessly. Now there’s ember-apollo-client for that so that's a lot easier.
-
-
exactly as you describe, it parses all the app's javascript looking for specially formatted imports. If I was redoing it today I would use knowledge from package.json rather than a special "npm:" prefix to determine which things should come from npm.
-
Is this something that could be added as an addon API?
-
@eaf4 you'd need to find imports that mapped onto things in package.json right? -
Allow me to raise a loud “please no” to continuing to do the `npm:` namespacing thing. It’s another oddity to document, and there’s more work to be done for every. single. package. imported from npm for TS (because automatic lookup of types fails without mapping in `paths`).

-
Maybe we can see about helping
@charles_demers update his addon to automatically find the appropriate packages? -
What he has there should actually Just Work™… once you have the stuff listed in your `ember-cli-build.js`. This is one reason I’m really excited about the Packagers stuff currently in progress for Ember CLI: it should make this kind of thing less bespoke.
-
It seems annoying to have to list it when you already said the same thing in your app via package.json + imports. Shouldn't be too hard to write a function that infers the right packages to add, right?
-
If we get “import from npm” working in the general case, TS consumers get everything they need for free 9 times out of 10. (Props to the
@typescriptlang team for making that true.)
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.