We've been running version 9.2.0 for several of our apps for a while now. For our newest app, we are looking at using the latest version of JET. When one of the developers installed the latest CLI, it prevented them from running any of our other applications locally. This is an issue not only for our developer experience, but will also cause issues on our JET Build server, since we need to support building both older and newer versions.
I tried installing the latest CLI with an alias in npm and the install worked:
npm install -g ojet12@npm:@oracle/ojet-cli
However, the alias I gave (ojet12) is not recognized as a command in powershell/command prompt. It seems like there is some other setup that happens during install that registers ojet as a command in npm which is not happening when using the alias.
Has anyone been able to get this working on their machines/servers?