install tooling tries to install Titanium CLI and SDK then fails #1246
Comments
|
Hello,
I went on a journey for the last hour or so! And I literally just solved my
issue.
the solution ended up being:
in a titanium project settings.json adding:
"terminal.integrated.env.linux": {
"PATH": "/home/skipper/.nvm/versions/node/v18.x.x/bin:${env:PATH}"}
that made the tidev addon recognise the CLI and SDK properly.
any questions about this issue/solutions please let me know
thanks for your attention in general,
João Silva
…On Wed, 27 Nov 2024 at 21:08, Ewan Harris ***@***.***> wrote:
Apologies for that @jdfabs <https://github.com/jdfabs>, if you try and
install the tooling manually does it work?
1. Install Node.js <https://nodejs.org/en/download/package-manager>
2. Install Titanium and Alloy CLI npm install titanium alloy -g
3. Install the latest Titanium SDK ti sdk install
—
Reply to this email directly, view it on GitHub
<#1246 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQADYXNWWS3D2PL34CTGA4D2CYYDBAVCNFSM6AAAAABSTVGUG6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBUG43TCMBQGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Oh that's interesting, the extension attempts to spawn Do the |
|
Yes, both ti and alloy work from linux terminal, the project files were
created with ti create. And yes, nvm is on the PATH, with the correct
version being referenced.
Another thing that might be of note is that after I added the path to the
settings.json on the first project (created with ti create)
I deleted the project and rebooted, and when loaded vscode tidev was still
working as expected.
One of the things that I tried doing was to go into vscode the
extension settings and manually set the path, which I found that was not
actually a setting, maybe that's an useful thing to add to the extension.
Once more, thanks for the attention,
João Silva
…On Wed, 27 Nov 2024 at 22:09, Ewan Harris ***@***.***> wrote:
Oh that's interesting, the extension attempts to spawn ti and alloy CLIs
to determine whether they are installed so your fix explains the error.
Do the ti/alloy commands work outside of VS Code? The fix suggests that
the nvm directory isn't on the PATH which to me would indicate they
shouldn't, the nvm install script *should* set a line in the correct
shell profile
<https://github.com/nvm-sh/nvm#installing-and-updating:~:text=Running%20either%20of%20the%20above%20commands%20downloads%20a%20script%20and%20runs%20it.%20The%20script%20clones%20the%20nvm%20repository%20to%20~/.nvm%2C%20and%20attempts%20to%20add%20the%20source%20lines%20from%20the%20snippet%20below%20to%20the%20correct%20profile%20file%20(~/.bash_profile%2C%20~/.zshrc%2C%20~/.profile%2C%20or%20~/.bashrc).>
to source the script which I think would ensure the npm installed tooling
is in the PATH. Maybe that's not set?
—
Reply to this email directly, view it on GitHub
<#1246 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQADYXMSSUN3QNFAPYFM6VT2CY7H7AVCNFSM6AAAAABSTVGUG6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBUHA3TSNJVG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Type: Bug
Can't find any way to make the tooling work.
Extension version: 1.3.0
VS Code version: Code 1.95.3 (f1a4fb101478ce6ec82fe9627c43efbf9e98c813, 2024-11-13T14:50:04.152Z)
OS version: Linux x64 6.9.3-76060903-generic
Modes:
System Info
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: disabled_software
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off
webnn: disabled_off
A/B Experiments
The text was updated successfully, but these errors were encountered: