I think the issue though is that for better or worse there is a clear signal that The Core Team Has Agreed that JSONAPI is The Winner, and that the most GraphQL fans can hope for is that _some_ of the functionality of GraphQL will eventually translate to future JSONAPI features..
-
-
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
-
Would it work to have the same `"npm:foo"` requirement as in ember-browserify?
-
Maybe if there was a build step to walk the AST to find imports with "npm" and add those to the requirements
-
@eaf4 how does ember-browserify do it? -
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`).

- 4 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.