Add support for element projects

[43081j]

Description

We should add support for element projects. The docs and this project are heavily tied into "app" projects (hence "shell" and such in the config).

Example use case:

If i have a small library of elements which are all written in typescript (especially appropriate for polymer 2.x), i'll need a build process somewhere to transpile them and lint them.

How?

We should be able to have polymer-build in our gulpfile, which does the same splitting as with an app project.

The difference being, we have no entrypoint or shell and likely need no bundling strategy or service worker, but rather just output the single files as they were in the source. Although, we should probably allow for a bundled version too.

[brettpostin]

+1 for this.

Background Scenario

We have an internal suite of elements that are developed, tested and showcased within an internal gallery app project. Currently we build and deploy three element bundles from this project. We package them into a "core" element bundle, and two other "extension" bundles that can then be pulled into various other projects. Therefore we do not have an entrypoint or shell.

Problem

We have just upgraded this app to Polymer 2, and would like to upgrade the build tooling too. I have looked through the documentation and source, and cannot see a way to achieve the same bundling approach we currently have using vulcanize. It seems heavily focused around the PolymerProject concept which I don't think fits our existing use case. We also use Gulp, which too has a lack of documented guidance.

Any help or clarification would be welcome.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically closed after being marked stale. If you're still facing this problem with the above solution, please comment and we'll reopen!