Skip to content

update nodejs page #242

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

update nodejs page #242

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
74e3d8e
update nodejs page
m1ga May 16, 2025
9babe47
update version
m1ga Sep 23, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions ..._Started/Installation_and_Configuration/Titanium_Compatibility_Matrix/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,9 +11,7 @@ This document describes the system environments that are compatible with Titaniu

### Supported SDK releases

Some information about legacy Titanium SDK versions is included here solely for reference. Thus, only the following releases are officially supported:

* 12.5.0 - latest
Some information about legacy Titanium SDK versions is included here solely for reference. Thus, only the latest officially release is officially supported.

### Pre-release versions

Expand All @@ -37,7 +35,8 @@ The Java Development Kit (JDK) is required to build Titanium apps and modules fo

| Titanium SDK version | Min JDK version | Max JDK version |
| --- | --- | --- |
| 12.0.0 - latest | 11 | 17 |
| 12.8.0 - latest | 18 | 21 |
| 12.0.0 - 12.7.0 | 11 | 17 |

<details>
<summary><b>Unsupported version</b></summary>
Expand All @@ -62,17 +61,16 @@ See [Installing Oracle JDK](/guide/Titanium_SDK/Titanium_SDK_Getting_Started/Pre

## Node.js

To run all Titanium components, you must have Node.js 18 or later.
To run all Titanium components, you must have Node.js 20 or 22.

On Windows you will need to enable `dev mode` in the Windows settings in order to use Node correctly. [Official Website](https://nodejs.org/en/download/releases/)

### Supported version of node.js

| Unified CLI Version | Min Node Version | Max Node Version |
| --- | --- | --- |
| 12.6.0 - latest | 18.x | 22.x |
| 12.5.0 - 12.6.0 | 18.x | 20.x |
| 12.1.0 - 12.5.0 | 16.x | 20.x |
| 13.0.0 - latest | 20.x | 22.x |
| 12.6.0 - 12.8.0 | 18.x | 22.x |


See [Installing Node](/guide/Titanium_SDK/Titanium_SDK_Getting_Started/Prerequisites/Installing_Node.html) for details.
Expand All @@ -82,6 +80,8 @@ See [Installing Node](/guide/Titanium_SDK/Titanium_SDK_Getting_Started/Prerequis

| Unified CLI Version | Min Node Version | Max Node Version |
| --- | --- | --- |
| 12.5.0 - 12.6.0 | 18.x | 20.x |
| 12.1.0 - 12.5.0 | 16.x | 20.x |
| 10.0.1 - 12.0.0 | 14.x | 16.x |
| 9.0.0 - 10.0.0 | 12.13.0 | 15.x |
| 8.0.0 - 8.2.0 | 10.13.0 | 12.x |
Expand Down
35 changes: 3 additions & 32 deletions ...uide/Titanium_SDK/Titanium_SDK_Getting_Started/Prerequisites/Installing_Node.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,43 +5,14 @@ weight: '20'

# Installing Node

Node.js is required for several Appcelerator components, including the Titanium CLI, Alloy, and the API Builder. Node.js is also required to build the Titanium SDK.
Node.js is required for several Titanium SDK components, including the Titanium CLI and Alloy. Node.js is also required to build the Titanium SDK.

## Compatibility and download

To run all Appcelerator components, you must have Node.js 14.x or later.
To run all Titanium components, you must have Node.js 22.x or later.

On Mac OS X and Windows, if you have selected to install Titanium updates, Studio prompts you to install Node.js. On Linux, you need to manually install Node.js.
Check [Titanium Compatibility Matrix](/guide/Titanium_SDK/Titanium_SDK_Getting_Started/Installation_and_Configuration/Titanium_Compatibility_Matrix/) which version of Node.js is required for each Titanium SDK version.

| Operating System | Min Node Version | Max Node Version | Download Location |
| --- | --- | --- | --- |
| macOS / Windows / Linux | 14.X | 16.X | [Official Website](https://nodejs.org/en/download/releases/) |

## Installation

Before installing the CLI, you should decide where you want the Node Package Manager (`npm`) to install packages. By default `npm` installs into `/usr/local` on OS X and Linux, which requires that you run `npm` as root. This is not recommended. You can avoid having to run `npm` by doing one of the following:

* Make the `/usr/local` directory writable by all:

```bash
sudo chmod 777 /usr/local
```

* Set `npm` to install to your home directory, or another directory of your choosing by setting the `npm` prefix. For example, you can add the following to your `.bash_profile` or other initialization file:

```
export NPM_CONFIG_PREFIX=$HOME
```

Alternately, you can create a .npmrc file in your home directory with the following contents:

```
prefix=/path/to/home
```

Where _/path/to/home_ is the path to your home directory. Setting the `npm` prefix to your home directory causes the `npm` packages to be installed to `$HOME/lib/node_modules` and launch scripts are installed in `$HOME/bin`. `$HOME/bin` must be in your PATH.

If you change your prefix after installing `npm` packages, you will have to reinstall packages. If you change the permissions on `/usr/local` after installing packages as root, you may need to change the ownership of the `npm` cache folder, as described in [Troubleshooting npm Problems](#TroubleshootingnpmProblems).

## Using NPM packages in Titanium

Expand Down
16 changes: 0 additions & 16 deletions ...nium_SDK/Titanium_SDK_Guide/Titanium_Command-Line_Interface_Reference/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,22 +15,6 @@ Getting started with the CLI only requires two steps:

2. Install and configure the CLI.

### Install Node.js

The CLI requires Node.js 18 or later. It is highly recommended you use a LTS (long term support) Node.js release. If you don't have Node installed, install it from:

* [nodejs.org](http://nodejs.org)

Before installing the CLI, you should decide where you want the Node Package Manager (`npm`) to install packages. By default `npm` installs into `/usr/local` on OS X, which requires that you run `npm` as root. This is not recommended. You can avoid having to run `npm` by doing one of the following:

* Make the `/usr/local` directory writable by all: `sudo chmod 777 /usr/local`

* Set `npm` to install to your home directory, or another directory of your choosing by setting the `npm` prefix. For example, you can add the following to your `.bash_profile` or other initialization file: `export NPM_CONFIG_PREFIX=$HOME`

* In this case, `npm` packages are installed to `$HOME/lib/node_modules` and launch scripts are installed in `$HOME/bin`. `$HOME/bin` must be in your PATH.

For more information, see [Installing Node](/guide/Titanium_SDK/Titanium_SDK_Getting_Started/Prerequisites/Installing_Node/).

### Install and configure the CLI

1. Install the `titanium` CLI.
Expand Down