How to work package based?

[sebakerckhof]

Hello,

I'm trying out angular 2, but I like to work package-based.
So for example my bootstrap code is in
packages/frontend-core/client/app.ts

What is the path I have to use for System.import in my index.html? index.html is in the same location.

And what urls do I have to use as templateUrls in my view annotations?

[ShMcK]

There is a tutorial that may help.

Paths are all absolute, not relative. In other words, from the root. Templates must be suffixed with .ng.html.

- client
    \- index.html 
                      // System.import('client/app');
    \- app.ts 
                      // import {Example} from 'client/components/example/example';
                     // templateUrl: 'client/components/example/example.ng.html'
    \- components
        \- example
                 \- example.ts
                 \- example.ng.html

[sebakerckhof]

Yes, but this doesn't seem to work inside packages
Here is an example repo that shows the problem: https://github.com/sebakerckhof/ng2

[ShMcK]

Thanks for the example. Now I understand what you mean.

There are a number of problems happening here.

1. The TypeScript compiler is not compiling app.ts into app.js
2. Meteor 1.2 introduces a new module system, which may break the current TypeScript compiler

There's a better Angular2-Meteor solution in the works, which I hope will work with 1.2 and function within a package. As it stands now, there are several issues and limitations.

[sebakerckhof]

Is there already work being done to make the typescript compiler work with the new build API?

I just rewrote the scss package to the new build api, I could do the same for typescript of this is not yet being worked on

[ShMcK]

Any help would be great, but I'd have to get an update on any current progress.

I'll pass this conversation reference on to @Urigo who may know more.

[sebakerckhof]

Okay, I've updated https://github.com/sebakerckhof/ng2
It now has a meteor 1.2 compatible build plugin for ng.html templates.
All templates (including the in-package ones) are now available under their absolute path.

I also have an experimental 1.2-compatible typescript build plugin, but the typescript transpilation throws an error. If this wouldn't throw an error, typescript modules should be available under
sanitized_packagename/path in package.

E.g. file client/app.ts in package ng2:example, would be available under ng2_example/client/app.

I'd have to look why transpilation fails another time though.

[ShMcK]

Ah, for package paths :'s are replaced with _'s. That's good to know.

As for Typescript, there aren't any good solutions for the compiling. It either works with Angular 2, or Meteor, but not together. I lost a few days pursuing a solution without success.