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
When executing ui5 --version in a project that has a version of the UI5 CLI installed in it's node_modules directory (e.g. because of a (dev)dependency to @ui5/cli), that module shall be used over any globally installed version of the UI5 CLI. Even if the ui5 command technically invokes the global module.
Current Behavior
When the UI5 CLI is installed locally in a project as well as globally, depending on how it is getting invoked, a user might end up using an unexpected version (if two different versions have been installed).
Steps to reproduce the issue
Install the latest UI5 CLI globally: npm install --global @ui5/cli
Inside a project with a package.json, install an old version of the CLI: npm install --global @ui5/cli@0.1.0
Create an npm script for ui5 --version to the package.json
Execute ui5 --version directly and through the npm script
When running the global "ui5" command while a local @ui5/cli version is
installed for the current project, the local one should be preferred.
Fixes: #58
When running the global "ui5" command while a local @ui5/cli version is
installed for the current project, the local one should be preferred.
Fixes: #58
When running the global "ui5" command while a local @ui5/cli version is
installed for the current project, the local one should be preferred.
Fixes: #58
When running the global "ui5" command while a local @ui5/cli version is
installed for the current project, the local one should be preferred.
Fixes: #58
When running the global "ui5" command while a local @ui5/cli version is
installed for the current project, the local one should be preferred.
In this case an information will be logged to the console.
This can be disabled by setting an environment variable:
`UI5_CLI_NO_LOCAL=true`
`ui5 --version` now also displays the CLI location for better troubleshooting.
Fixes: #58
Expected Behavior
When executing
ui5 --version
in a project that has a version of the UI5 CLI installed in it'snode_modules
directory (e.g. because of a (dev)dependency to@ui5/cli
), that module shall be used over any globally installed version of the UI5 CLI. Even if theui5
command technically invokes the global module.Current Behavior
When the UI5 CLI is installed locally in a project as well as globally, depending on how it is getting invoked, a user might end up using an unexpected version (if two different versions have been installed).
Steps to reproduce the issue
npm install --global @ui5/cli
npm install --global @ui5/cli@0.1.0
ui5 --version
to the package.jsonui5 --version
directly and through the npm scriptContext
Affected components
The text was updated successfully, but these errors were encountered: