Skip to Content
Browse documentation

Manage Node.js Applications in UAPP

Review Node.js applications and change runtime, startup script, public directory, environment and sandbox lifecycle settings in UAPP.

Open Node.js → Node.js Applications. This page requires the Node.js selector feature.

Review website, runtime, startup script, public path, environment, deployment state, enabled state and available actions. The summary counts applications, enabled sandboxes, production/development environments and Ready/Deploying states. Search and sort to find the intended website.

Change Node.js runtime

  1. Select Change Node.js runtime.
  2. Check the website and current runtime.
  3. Choose a listed installed Node.js version.
  4. Choose whether to reinstall packages.
  5. Acknowledge that you backed up the application and package list, then save.
  6. Wait for work to finish and test startup and application requests.

The server validates the choice against the configured installed runtime list. A displayed inherited runtime does not allow entering an arbitrary version.

Reinstallation may affect dependencies. Skipping it does not guarantee that existing native modules or application code work with another runtime.

Edit application settings

ControlRequired value and effect
Startup scriptA filename such as app.js; starts with a letter or digit, followed by letters, digits, underscores or hyphens, ending in .js. No directory path, .mjs or .cjs entry is accepted by this form.
Public directoryRelative subdirectory beneath the website document root, such as public. This does not move the document root.
EnvironmentProduction or Development; rebuilds application service configuration.

Use the corresponding edit action, review the website and select Save Changes. The startup file must exist in the project.

Public-directory validation accepts 1–253 word characters, dots, slashes and hyphens, with no leading dot/slash or trailing dot/slash. Use a simple relative path without traversal components. Choosing Production does not replace application-specific security or configuration review.

Enable or disable

Select the sandbox switch and confirm Enable Node.js Sandbox or Disable Node.js Sandbox. The switch retains its current state until confirmation is submitted. This rebuilds service configuration; disabling does not delete the sandbox.

Reinstall

Select Reinstall Node.js sandbox. It reuses the current runtime. Review the warning and confirm that you backed up the application and package list. Recheck dependencies afterward; the confirmation warns that packages may be removed.

Delete

Select Delete Node.js sandbox and acknowledge the destructive action. It removes the sandbox environment and rebuilds service configuration. Website files are preserved, but the Node.js application will no longer run through that sandbox.

The panel removes Node.js application settings and resets the application/runtime selection to defaults. Since project files are preserved and NPM uses the document root, do not assume this also cleans every project dependency or file.

Keep a recovery path

Deletion is different from disabling. Keep the project, dependency manifests, lockfiles and required data backed up before deleting or reinstalling.

Busy or failed operations

Deployment in progress suppresses lifecycle actions and is checked before mutations. Wait and refresh; ask the provider to inspect a stuck deployment rather than repeatedly submitting changes.

If a rebuild fails, newly recorded settings may remain. Check current values before retrying. Sandbox deletion is blocked in demo mode. Use NPM Management for dependency changes.