docs: 3rd Party Library Design Doc.

[hansl]

No description provided.

[jkuri]

thanks for this. lgtm

[cironunes]

minor: SystemJS

[hansl]

Done.

[filipesilva]

I really like the appData bit. Not so much the hooks bit though.

I can't imagine that a lib that uses these hooks could be used without angular-cli, and that leads to a divide we are trying to avoid - having angular2-* versions of libs.

All these configuration options also seem to severely be overloading package.json. It is not hard to imagine that an app using 4-5 libraries would have the majority of it's package.json occupied by angular-cli module configuration. At that point, it's better to simply have an angular-cli.json file.

Perhaps the key issue here is the separation of cli addons vs simple libraries. Addons should change the functioning of the CLI, whereas simple libraries should be no more than imported and perhaps have some simple prompts for automatically add providers/configuration to an app.

[filipesilva]

It feels a bit superfluous to have a strong commitment to SystemJS (for the CDN functionality) and still keep the brocolli build step.

Perhaps we could move to SystemJS TS browser compilation for dev builds, and have the production build step simply compile TS to spare SystemJS from doing it.

[hansl]

We have no strategy for a production build, but it will involve concatenating + minifying, so it's safe to say we'll have to revisit broccoli.

[hansl]

@wesleycho you said you wanted to take a look at this proposal.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}