Currently, the NativeScript NPM ecosystem is scattered with no convention guidelines.

NativeScript packages can come in flavours and can be easily categorised.
For example:

• Plugins
• Adapters
• Adapter plugins
• Dev (Toolchain / build process hooks)

And more...

Here are some real world examples of packages:

• nativescript-socketio - Plugin
• nativescript-angular - Adapter
• nativescript-ng2-magic - Adapter plugin (angular)
• nativescript-dev-sass - Toolchain
• nativescript-dev-typescript - Toolchain

The list is long and growing...

I believe its important to organise most of the packages under a domain of some sort, similar to the way it is done by the Angular 2 team.

Some samples:

@nativescript/core ==> nativescript
@nativescript/angular/core ==> nativescript-angular
@nativescript/angular/magic ==> nativescript-ng2-magic
@nativescript/dev/typescript ==> nativescript-dev-typescript

Transition can be done in parallel where a new version is published into old and new name.

Of course other ways to categorise are welcome, this is just an idea.

For example, separate official telerik modules by having @telerik/nativescript or @tns/core

I think it will greatly help making some sense.

If top contributors such as @NathanWalker , @NathanaelA , @vakrilov , @triniwiz and many others will lead the way it will get adoption.