I'm 100% guilty of over-defending JSONAPI relative to GraphQL without having any personal experience using it (sorry again @DevinRhode2).
-
-
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.
-
That said, I think the work being done to import npm packages more easily in apps is gonna open up experimentations outside of Ember’s conventions a lot.
-
I think that supporting nom packages natively is one of the highest leverage things Ember can do. Curious: did you try Ember Browserify?
-
I did, it works well for certain packages but the apollo-client toolset makes heavy use of named exports and ember-browserify doesn't support them...
-
Interesting. Can you say more about what exactly failed?
-
Imports like `import {InMemoryCache} from 'apollo-cache-inmemory';` didn’t work. We ran into this problem only when we wanted to adopt apollo 2.0 and ember-apollo-client was still on 1.0. I ended up creating this addonhttps://www.npmjs.com/package/ember-cli-webpack-imports …
-
Oh nice! Is this a general replacement for ember-browserify?
-
More or less because you have to know in advance all the things you want to import and define them in ember-cli-build.js
- 11 more replies
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.