Monitor the Upload and View the Published Package(s)

VB Studio initiates the upload process and progressively shows the status as it occurs.

1. After you click Publish to NPM, the tarball files are scanned for viruses.

   If any tarball files are determined to be unsafe, the Antivirus scanning of attachment failed error message is displayed.

2. If the tarball files are determined to be safe, the tarball content is examined, looking for the package.json file, which is parsed if found.

   If the package.json file isn't found in the tarball file, or if the internal package.json file cannot be parsed, if the option to Use Selected Tarball(s)'s internal package file was selected for the package layout option, the Unable to find or parse correctly the package archive (package.json) within the tarball content error message will be displayed.

3. The project's NPM registry is checked to see whether it already has same version of package.

   If it does, the Package already exists and cannot be overwritten error message will be displayed.

4. If the Generate or update metadata files option was selected, the NPM registry is checked for an existing package metadata file (or files).

   If package metadata is already available, that metadata is retrieved and the package metadata is updated with the new version. Otherwise, a new package metadata is created. Creating and updating this metadata is based on the tarball file’s internal package file and the user-specifed value for the custom layout option.

   The new version of the metadata file is created, based on the tarball file’s internal package file and the user-specifed value for the custom layout option.

5. The tarball is put into the project’s NPM registry.
6. The aggregated package metadata is put into the project’s NPM registry and the aggregated package metadata is uploaded.
7. The version metadata is added to the project’s NPM registry.

   The status(es) of successful, partial, and failed upload(s) are displayed.