Skip to content

Stress test: investigate need for multiple Typescript loaders in Webpack config #24306

Description

@spmonahan

Currently we use multiple Webpack loaders to process .ts/tsx files in our performance application. We do this because FAST Web Components do not build properly with babel-loader so we conditionally load them with ts-loader. Using ts-loader allows Web Components to correctly build but it's not ideal as our Webpack config is more complex.

Investigate this issue with the goal of loading all code via swc-loader.

See: #24279 (comment)

Metadata

Metadata

Assignees

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions