Bug Fix | Rules | babel loader not working as intended in most cases, tsloader must be used | |
Bug Fix | Context | both for loaders used in 'rules' export, and for ts-fork-checker plugin, context is ont set, causing builds that define a context directory to something other than the root project directory to fail | |
Bug Fix | Testsuite | the 'test-suite' plugin is not getting included in the build output | |
Bug Fix | Externals | regression - css and sass imports in a webapp project are getting flagged as external, and compilation fails at 'seal' stage | |
Bug Fix | Externals | regression - css and sass imports in a webapp project are getting flagged as external, and compilation fails at 'seal' stage | |
Bug Fix | Imports | when importing package modules whose exports are defined by the 'exports' field in it's package.json, the 'default' exports are always used regardless of the executing build's target platform | |
Bug Fix | Tsconfig | module resolution is falling back to 'default' when resolving package.json 'exports' field for entry points, regardless of 'module' type set in tsconfig.json | |
Bug Fix | Optimization | the 'eslint' cache group is not working | |
Bug Fix | Externals | non-relative imports from vendor node_mdules are always bundled regardless of whether the 'externals' regex matches the module name | |
Bug Fix | Types | bundle file contains invalid module paths and no top level export if project uses default exports in entry file(s) | |
Bug Fix | Types | declaration name replacements for an aliased module path always use first alias path specified in 'paths' array and does not check any additional to ind correct path to use | |
Bug Fix | Resource | when a file is used as an input, adding as a build asset fails, and build fails | |
Feature | Config | add new base rc config 'type' where a configuration can be defined for all builds of a particular type i.e. 'app, 'lib', etc, can be applied, at both a global level and/or the environment level | |
Feature | Schema | add support for a base configuration definition that gets applied to build configs according to library type | |
Feature | Tsconfig | add support for semi-auto construction of typescript build configuration and compiler options using only one tsconfig.json file for multiple builds with multiple target platforms | |
Feature | Target | add support for specifying more than one webpack target for a single build | |
Feature | Resolve | add initial support for polyfils in non-node / web target types | |
Performance Enhancement | Rules | babel configuration modifications and cleanup reduce output file size by 5%-8% for most files tested | |
Performance Enhancement | Tsc-service | finalizing changes in tsc service, cuts down tsconfig creation by ~ 8% | |
Refactoring | Startup | add dump of tsconfig info on startup exit on error | |
Refactoring | Config | add new rc property 'autoConfigure' to sourcecode options object to support manually enabling or disabling auto-configuration of the ts runtime profile | |
Refactoring | Types | remove all comments in dts output bundle | |
Refactoring | Config | change parsing of spmhrc file definitions to use 'merge' of section levels as opposed to 'mergeStrong' | |
Refactoring | Exports | update tsconfig and npm package files to latest convention for exports, transpilatin, code bundling and release configuration | |
Refactoring | Tsc | add ts defined base configurations for each target, to be applied and/or referenced when dynamically constructing a build's tsconfig | |
Refactoring | Minimizer | set 'safari10' flag on terser options when build loader is 'babel' | |
Refactoring | License | add vendor plugin 'license-webpack-plugin' for enhanced license extraction as compared to terser plugin | |
Refactoring | Experiments | add support for configuring 'experiments' wp export in rc file | |
Refactoring | Experiments | add new vendor mod to force angular builds to support top-level await |