In general, the idea is to have the names be as detailed as possible without being overly complicated. Ideally, it will be clear to tell from the naming of the package, if the package is related to UI/API tools, which product it is (eg Naslag, Fiscal) and finally a name describing it's name and functionality.

How should NPM packages be named?

Examples: @Nextens-Karate/API-ProductZone-Name of package @Nextens-Karate/API-Naslag-IDSManagementTemplate -> This is an example of what the name of an NPM package could be.

@Nextens-Karate = This determines the scope of the package within the feed. A feed could contain multiple packages from NPM packages to Nuget packages or even just jar files. By using the scope it makes it clear to everyone that this package is an NPM package related to Karate. Most importantly, whenever you type @Nextens-Karate into the search it will show every NPM package that is related to Karate that is currently available to use.

API/UI = After determining the scope of the file, write API for tools related to Karate API testing and UI for tools related to Karate UI. This makes it instantly clear that the package is either API or UI and easier for anyone searching for tools related to APIs or UI to find what they need.

ProductZone = ProductZone is where you name which product this package is related to. This could be any product in Nextens, for example: Naslag, Fiscal, Reporting, Datahub, API platform etc.

Name of package = Naming the package should be as descriptive as possible, but also not overly complex or long. Short and to the point is key, as seen in the example above. IDSManagementTemplate is a clear name, it makes it clear that the package is a template for the IDSManagementAPI as it is an API package as determnied in the API/UI aspect of the name.