Feature package structure and publishing

[tomermes]

moved from another project (#143)

Currently we do not define the way in which feature packages (npm packages) expose their inner parts, and how those exports would be consumed by a user.

tomrav: New file suggestion: index.[feature-name].[targetRuntime].ts These index files are used to export additional content from the feature package. e.g. components, typings, drivers, reusable configurations and more Each target runtime will result in a separate bundle, assuring that environment specific code will not be included where it is not needed, and should not run These files can be found in both the src and test-kit directories of a package Allowed target runtime values are: browser, node, worker and universal It remains an open question how exactly an import from these files would look like and what project structure actually gets published to NPM.

tomrav: AviVahl any thoughts about how up to date this issue is? I believe we've solved the publishing issue for now, not sure if the particulars are documented anywhere.

AvIVahl Issue is still relevant. typescript gets into main/preview bundles quite often because of that.