Skip to content
Verified

Dependencies

The npm packages a project uses, checked live against the npm registry.

A dependency is a package name and a version spec, saved on the project. Everything else on the row (the description, the latest version, and the status) is read live from the npm registry.

The table

Changing dependencies

Add a package

Click Add dependency and search npm by name. Picking a result adds it at its latest version.

Pick a version

Click a row's version to open a searchable list of every published version of that package.

Save

Changes are staged, not saved immediately. A dirty bar appears at the bottom with Reset changes and Save changes.

Removing a package that was already saved marks it Deleted rather than dropping the row outright, and stays reversible (Restore) until you save. Refresh re-checks every package's status against the registry.

Saving can take a moment

Saving runs npm install for the project, so it can take longer than a typical save. If the npm registry is unreachable, the table still shows and stays editable, with statuses marked Unknown until it recovers.