You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Resolves: SAP/ui5-tooling#809
When shimmed packages are defined as dependency aliases in the
package.json, they are being excluded from the bundlig as the packager
eventually finds the real package and its path and as it's not defined
in the shim, but its alias, it gets ignored.
We need to provide more robust discovery in order to handle those cases:
- npm/cli#3
-
https://github.com/npm/rfcs/blob/main/implemented/0001-package-aliases.md
Expected Behavior
Automatic dependency analysis should be able to pick up exposed name of npm dependency, regardless of the underlying package.
Current Behavior
If one runs
npm i kool@npm:case
and then provides shim configuration forkool
, the tooling won't pick it up.Steps to Reproduce the Issue
Context
ui5 --version
when using the CLI):3.0.5
16.19.1
8.19.3
Win11
not relevant
nothing
Log Output / Stack Trace
I can provide additional log traces / info if needed.
The text was updated successfully, but these errors were encountered: