Packager RFC

[chadhietala]

Rendered HTML

[stefanpenner]

drop -> place

[stefanpenner]

resovle -> satisfy

[dschmidt]

1. Is this only about imported dependencies or are you already going to handle dependencies of templates in this step (like helpers/components/etc)? Tbh I don't know how HTMLbars templates work: Do they already import everything that is needed so it's not even a special case for you to handle?

App and addon resolution uses the dep-graph.json to start the traversal. By default, the Pre-Packager uses the App as the entry into the graph, but developers can supply N entries. More on this later, but for now you should think of an entry as a large functional area of an application (the admin section, the main app, etc). 

and

  entries: ['my-app'], // Optional if you're only building your app

Can you elaborate a bit more on this? Are you planning on enabling mutliple apps per project? I want to create embeddable widgets off a large application. It of course should not load all the templates and dependencies of the main application.
I'm currently checking out options for this, engines might be one solution when they land - but that seems a bit farther ahead than this.
Moving everything that is shared between main app and widgets into an addon is very cumbersome and seems hackish if I want to keep a certain level of convernience while developing both apps at once.
So if this would enable me to build an app.js and a widgets.js with corresponding .html files in the same project but based on different entry points, that would be more than awesome.

[rwjblue]

We are working on closing the ember-cli/rfcs repo in favor of using a single central RFC's repo for everything. This was laid out in https://emberjs.github.io/rfcs/0300-rfc-process-update.html.

Sorry for the troubles, but would you mind reviewing to see if this is still something we need, and if so migrating this over to emberjs/rfcs?

Thank you!