Strong confirm on @chriskrycho (et al)'s amazing work. I mention elsewhere though that TS doesn't compete with another feature/claim that Ember offers, but merely fills a void. I believe there's maybe a messaging issue that discourages folk from seriously investigating GQL.
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`).

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