These are chat archives for systemjs/systemjs

9th
Jan 2016
Adam Reis
@adamreisnz
Jan 09 2016 04:34
@peteruithoven my editor is complaining when I try to do a import { SomeComponent } from 'app/components/some-component’ from my boot file located in the app/ folder. Changing it to ./components/some-component works. This is with typescript btw.
Jeremy Danyow
@jdanyow
Jan 09 2016 14:18

@adambuczynski :point_up: January 8, 2016 4:34 PM create a module that exports all the other stuff:

all-the-things.js

export * from 'my-module';
export * from 'my-other-module';
export * from 'another-one';
export * from 'dont-forget-this-one';
then import {SomethingFromMyModule} from 'all-the-things';
Adam Reis
@adamreisnz
Jan 09 2016 18:07
It would be a nightmare to maintain that for your entire application...
Peter Uithoven
@peteruithoven
Jan 09 2016 19:13
@adambuczynski I can imagine that your editor (or some of it's plugins) don't understand or talks to SystemJS, but isn't really a SystemJS problem?
Adam Reis
@adamreisnz
Jan 09 2016 19:15
You’re right, but I assumed there would be more developers with the same problem/query, especially since you’d want systemjs to understand the same import/export logic
Peter Uithoven
@peteruithoven
Jan 09 2016 19:18
True, but I would advice opening an issue in the relevant editor / plugin
Adam Reis
@adamreisnz
Jan 09 2016 19:50
Thanks, however it’s not an editor specific bug/issue, it’s a generic query regarding ES6/typescript module resolution and using base app module names. I will keep digging though and try to find a solution that works for me.