Releases: SAP/ui5-project
v3.0.1
Bug Fixes
- Prevent socket timeouts when installing framework libraries
a198356 - Library: Do not throw for missing .library file
1163821 - Project#getReader: Do not apply builder resource excludes for style 'runtime'
1cd94f7 - TaskUtil: Provide framework configuration getters to custom tasks (#580)
6a40927 - graph: Always resolve rootConfigPath to CWD
ef3e569 - projectGraphBuilder: Apply extensions of the same module only once
6d753a8 - ui5Framework: Improve error handling for duplicate lib declaration
fb1db6d
All changes
v3.0.0
Breaking Changes
- Implement Project Graph, build execution
161f462 - Run 'generateThemeDesignerResources' only on framework libs
e4bb108
BREAKING CHANGE
Support for older Node.js and npm releases has been dropped for all UI5 Tooling modules.
Only Node.js versions v16.18.0, v18.12.0 or higher as well as npm v8 or higher are supported.
All packages have been transformed to ES Modules. Therefore modules are no longer provides a CommonJS exports.
If your project uses CommonJS, it needs to be converted to ES Modules or use a dynamic import for consuming UI5 Tooling modules.
For more information see also:
-
https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c
-
normalizer and projectTree APIs have been removed. Use generateProjectGraph instead
-
Going forward only specification versions 2.0 and higher are supported
- In case a legacy specification version is detected, an automatic, transparent migration is attempted.
-
Build:
- The "dev" build mode has been removed
- The task "generateVersionInfo" is no longer executed for application projects by default. You may enable it again using the includedTasks parameter
Features
- specVersion 3.0 (#522)
c5070e5 - Introduce SpecificationVersion class (#431)
e57842b - TaskRunner: Provide taskName and logger instance to custom tasks
36cd2d8 - TaskUtil: Add resourceFactory API to v3 interface
2e863cf - TaskUtil: Add getProject/getDependencies API to interface
51f2949
Bug Fixes
- npm/Installer: Do not wrap promise provided by rimraf v4
2d1ccda - ProjectBuilder: Fix verbose logging for already built projects
f04ffd2 - ProjectBuilder: Skip build for projects that do not require to be built
ac5f1f8 - Specification: Fix migration for legacy projects that are not applications or libraries
d89d804 - Fix build manifest creation
b1459eb
Dependency Updates
All changes
v3.0.0-rc.9
v3.0.0-rc.8
Breaking Changes
Bug Fixes
- Registry: Do not use custom logger for pacote
242601f
Features
BREAKING CHANGE
For projects and extensions defining specVersion 3.0 and later, the
metadata.name property must satisfy the following conditions:
- Must be at least 3 characters long
- Must be no longer than 50 characters
- Must contain lowercase characters only
- Must contain alphanumeric characters, dash, underscore and period only
- Exception:
@and/are allowed at certain positions as
explained below
- Exception:
- Must start with an alphabetic character or an
@-character - If a name starts with an
@-character, it must contain exactly one
forward-slash/- This is aligned with the npm concept for package scopes