Charles

Based on what you have described, what would the `deployUrl` option need to do with its value to meet the needs of the application? For instance, is the Angular CLI...

Specifying the intended extension would most likely be the best option currently in this case (`@progress/kendo-theme-bootstrap/dist/all.scss`). The behavior of Sass deep importing into a package reference is unfortunately not well-defined...

Thank you for taking the time to try out the experimental esbuild-based builder. To provide some more insight into the Angular/TypeScript compiler elements of the build process, you can run...

This is currently expected behavior. While not ideal, each locale's data has a minimal size and will feature some additional upcoming size reductions. Additionally it typically compresses well. Also, we...

The ideal solution would be for the packages in use to provide browser support directly. However, this may not be possible or on the roadmap for some packages. In that...

This doesn't solve the dynamic import issue you are having but that information is available directly from the browser via the `Intl` API. For display names: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/DisplayNames As to the...

Thank you for the reproduction. That "Files not registered..." error seems to be StackBlitz related. If you add `"files/*.ts"` to the `include` option in the `tsconfig.app.json`, that code should build...

Upon further investigation, I believe i have tracked down what you are encountering. The lack of an extension within the import expression appears to be the problem. The dynamic import...

Due to the experimental status of the builder and the potential for internal changes, we are not currently exposing a similar set of transformation options. However, as the builder moves...

After talking over the issue internally, we would like to avoid adding to the public API surface if possible. Code duplication in the final output bundles of the packages shouldn't...