[ ] Unit or Functional tests are included in the PR
Description:
Adds support for building a custom element that is defined with the new decorator, and fixes a couple minor issues with the existing custom element build:
If building a custom element in a dependency, the --element flag will not end in .ts. Previously this meant that the prefix name could not be automatically determined; this updates it so that it works in either case.
templates/custom-element.ts is compiled with a target of es6 (as are all the ts files), but it gets fed through uglifyJS and runs in the browser. Using let breaks this file, and it probably shouldn't be run through that pipeline if doing something perfectly valid in the source file creates invalid output. Now it's a JS file
Type: feature
The following has been addressed in the PR:
Description:
Adds support for building a custom element that is defined with the new decorator, and fixes a couple minor issues with the existing custom element build:
--elementflag will not end in.ts. Previously this meant that the prefix name could not be automatically determined; this updates it so that it works in either case.templates/custom-element.tsis compiled with a target of es6 (as are all the ts files), but it gets fed through uglifyJS and runs in the browser. Usingletbreaks this file, and it probably shouldn't be run through that pipeline if doing something perfectly valid in the source file creates invalid output. Now it's a JS file