Closed davidchieregato closed 2 years ago
I just upgraded the cli from 3.2.0 to 4.1.0, and no issue encountered. I'm using Node.js 16.13.1 and npm 8.5.5 on MacOS. Not sure if it makes a difference. Since @loopback/cli@4.1.0 was published yesterday, maybe you want to give it a try?
npm list -g
/usr/lib
├── @loopback/cli@4.1.0
I found out that lb4 -v is not consistent with the version shown by npm, it seems that npm actually updated the cli globally, but the lb4 command doesn't get the correct version
lb4 -v
@loopback/cli version: 3.2.0
Any lb4 command still shows update available from 3.2.0 to 4.1.0
Update: platform following Node v16.14.2 npm 8.12.1 WSL2 Ubuntu 20.04 on Windows 11
That's strange. Here is my output for lb4 -v
:
$lb4 -v
@loopback/cli version: 4.1.0
@loopback/* dependencies:
- @loopback/authentication: ^9.0.1
- @loopback/boot: ^5.0.1
- @loopback/build: ^9.0.1
- @loopback/context: ^5.0.1
- @loopback/core: ^4.0.1
- @loopback/metadata: ^5.0.1
- @loopback/openapi-spec-builder: ^5.0.1
- @loopback/openapi-v3: ^8.0.1
- @loopback/repository-json-schema: ^6.0.1
- @loopback/repository: ^5.0.1
- @loopback/rest: ^12.0.1
- @loopback/testlab: ^5.0.1
- @loopback/docs: ^5.1.0
- @loopback/example-hello-world: ^5.0.1
- @loopback/example-log-extension: ^5.0.1
- @loopback/example-rpc-server: ^5.0.1
- @loopback/example-todo: ^6.0.1
- @loopback/example-soap-calculator: ^5.0.1
- @loopback/service-proxy: ^5.0.1
- @loopback/http-caching-proxy: ^4.0.1
- @loopback/http-server: ^4.0.1
- @loopback/example-todo-list: ^6.0.1
- @loopback/dist-util: ^0.4.0
- @loopback/rest-explorer: ^5.0.1
- @loopback/eslint-config: ^13.0.1
- @loopback/example-express-composition: ^5.0.1
- @loopback/example-greeter-extension: ^5.0.1
- @loopback/booter-lb3app: ^4.0.1
- @loopback/example-lb3-application: ^5.0.1
- @loopback/example-greeting-app: ^5.0.1
- @loopback/example-context: ^5.0.1
- @loopback/repository-tests: ^0.21.1
- @loopback/health: ^0.11.1
- @loopback/authorization: ^0.12.1
- @loopback/rest-crud: ^0.15.0
- @loopback/security: ^0.8.1
- @loopback/authentication-passport: ^5.0.1
- @loopback/example-metrics-prometheus: ^0.10.1
- @loopback/metrics: ^0.11.1
- @loopback/model-api-builder: ^4.0.1
- @loopback/logging: ^0.9.1
- @loopback/example-access-control-migration: ^5.0.1
- @loopback/example-file-transfer: ^4.0.1
- @loopback/example-rest-crud: ^4.0.1
- @loopback/apiconnect: ^0.10.1
- @loopback/example-validation-app: ^4.0.1
- @loopback/cron: ^0.9.1
- @loopback/example-multi-tenancy: ^0.13.1
- @loopback/example-passport-login: ^4.0.1
- @loopback/authentication-jwt: ^0.12.1
- @loopback/context-explorer: ^0.8.1
- @loopback/express: ^5.0.1
- @loopback/example-todo-jwt: ^4.0.1
- @loopback/mock-oauth2-provider: ^0.6.1
- @loopback/pooling: ^0.8.1
- @loopback/typeorm: ^0.7.1
- @loopback/example-graphql: ^0.7.1
- @loopback/graphql: ^0.8.1
- @loopback/filter: ^3.0.1
- @loopback/rest-msgpack: ^0.8.1
- @loopback/example-binding-resolution: ^0.7.1
- @loopback/example-webpack: ^0.8.1
- @loopback/example-socketio: ^0.6.1
- @loopback/socketio: ^0.6.1
- @loopback/monorepo: ^0.5.1
- @loopback/tsdocs: ^4.0.1
- @loopback/example-references-many: ^6.0.1
It seems to have the latest.
I'm not sure what suggestion I could make other than uninstall/reinstall @loopback/cli
globally.
So, it seems that the problem is not related to loopback but it has something to do with how linux manages /usr/bin and /usr/local/bin, I solved it by removing manually the lb4 binary, npm uninstall would not remove it.
which lb4
/usr/local/bin/lb4
sudo rm -rf /usr/local/bin/lb4
sudo npm install -g @loopback/cli
lb4 -v
command not found
which lb4
/usr/bin/lb4
hash lb4
//hash drops executable location hash to update the path
lb4 -v
@loopback/cli version: 4.1.0 @loopback/* dependencies: - @loopback/authentication: ^9.0.1
...
Describe the bug
Hello,
When I run any lb4 command I get prompted about cli compatibility
And later after skipping updates which would downgrade everything I get the notice that an update for the CLI is available:
and after running the command it will stay at 3.2.0 without updagring,
npm outdated -g
also doesn't show any update available.I also added
In.
.yo-rc.json
but it will still show generated by @loopback/cli@Logs
Additional information
No response
Reproduction
issue is obvious