Manage Node.js NPM Packages in UAPP
Install, update and remove website NPM packages in UAPP, including scoped names, version syntax, bulk actions and confirmation.
Open a website from Node.js → NPM Management, or use its package action in Node.js Applications. The website must belong to your account and the Node.js Apps feature must be enabled.
Install packages
- Enter one or more packages in the package text field.
- Separate entries with newlines or commas.
- Select Install Packages.
- Review the website, selected names and count.
- Confirm, wait for processing and refresh the installed list.
Examples accepted by the panel's validator:
express
lodash@4.17.21
@types/node@^22Unscoped names and scoped names such as @scope/package are accepted. Name and scope components start with a lowercase letter or digit and may continue with lowercase letters, digits, dots, underscores and hyphens.
An optional @version suffix accepts letters, digits, dots, asterisks, comparison symbols, carets, tildes, plus signs and hyphens. The panel validates syntax; package/version availability and compatibility are checked by the package operation.
Do not paste package.json, shell commands, URLs, Git references, local paths or command-line options. Spaces and multi-part ranges are not accepted by this form. Entries are trimmed, deduplicated and sorted before task submission.
Review installed packages
The table shows package names, versions and actions. Search or sort to locate a dependency. The package listing and operations use the website document root as the NPM prefix with the website sandbox's NPM executable.
Update packages
Use the individual update action, or select packages and choose Update Selected. Review the package list and confirm. The backend submits NPM update work. Inspect resulting versions and test the application rather than treating a started message as completion.
Remove packages
Use the individual remove action or Remove Selected. Review the selected website and packages, acknowledge that removal may stop the application, then confirm.
Dependency changes affect the application
Check the project's direct and indirect dependencies before updating or removing packages. Preserve application files, package.json and any lockfile used by the project. The panel does not establish that a dependency change is compatible with your code.
Removal is explicitly blocked in demo mode in the reviewed handler. Installation and updates do not share that explicit check there.
Busy or failed work
Operations check for a deployment already in progress. Wait before submitting another change. A started message confirms task submission, not successful package installation.
If the installed list stays unchanged or startup fails, ask the provider to inspect package output and verify runtime compatibility. Avoid repeated submissions while a task may still be running.