1. Using Visual Builder Studio
  2. Maximize the Power of Your Project
  3. Use the Project's NPM Registry
  4. Browse and Search Packages in Your Project's NPM Registry

Browse and Search Packages in Your Project's NPM Registry

From the NPM page, you can browse the project's NPM registry or search for and locate packages in the registry.

With Browse selected, you can display and select packages, then view details about the packages in the Info section, under Registry Details. You can select just one package, or use Select All to select all packages. You can also select Invert Selection or Delete.

When the list of items is long, you can sort by Name, Size, and Last Updated, in ascending or descending order:

NPM Browse window sort categories, in ascending or descending order

The sort settings will be remembered for the duration of the session, but will revert back to the default setting after a new browser window is opened. Being able to sort this way can be very useful when you want to analyze artifacts for retention, based on their size and how frequently they have been used, which you can see from the last updated date.

You can select a file and see details in the panel on the right. The panel can display up to three categories of details, including Info at the top and Dependencies at the bottom, with tabs for Default, Optional, Dev, and Peer views. If there are too many dependencies to list in the display, click the Download Download, then open and examine the file.

If you uploaded the package by executing a build job or a pipeline, a third category, Build Details, will be displayed between the other two.

Here's an example showing build details for a package that was uploaded by a user-initiated job:

Description of npm_build_details_job.png follows
Description of the illustration npm_build_details_job.png

Note:

You can only view and examine build details for published Node.js packages in the NPM page if you select a build executor template that contains one of the following Node.js versions from the software catalog:
  • Node.js 17(Version 17.6.0)
  • Node.js 16 (Version 16.14.0)
  • Node.js 14 (Version 14.19.0)

Here's an example showing build details for a package that was uploaded by a pipeline:

Description of npm_build_details_pipeline.png follows
Description of the illustration npm_build_details_pipeline.png

If the selected package has been deprecated, its details will be displayed under Deprecation Details, in the Package Details panel. These details could include a message provided by the author when the package is being deprecated, such as "Version no longer supported because it used outdated code".

You can use the page's basic search capability by entering a search string, then using All or Files to filter the results.

You can use Package Search to use the Name, Keywords, Version, or Author fields to search for a package in the registry. The asterisk (*) can be used as a wildcard character. To improve performance, specify your search criteria as precisely as possible.

To narrow your search results, select Show Advanced Options, then click Search. These are the options you can specify:

  • Size: Specify the Min and/or Max package sizes to search. The sizes could range from KB to GB.
  • Updated: Use Since and/or Before by entering the date in mm/dd/yy format or by selecting it using the calendar.

Search results can be returned under two views, packages or files.

To delete a file or package that was returned by the search, select the checkbox next to the package or file you want to delete, then click Delete. When you're asked to confirm, press Yes, Delete All.