Skip to content

Commit eb3b779

Browse files
committed
Adding a quick section on where to find {N} plugins
1 parent 87cca66 commit eb3b779

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

PLUGINS.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,7 @@ PLUGINS
44
Starting with NativeScript CLI 1.1.0, you can develop or use plugins in your NativeScript projects.
55

66
* [What Are NativeScript Plugins](#what-are-nativescript-plugins)
7+
* [Where Can You Find NativeScript Plugins](#where-can-you-find-nativescript-plugins)
78
* [Create a Plugin](#create-a-plugin)
89
* [Directory Structure](#directory-structure)
910
* [`package.json` Specification](#packagejson-specification)
@@ -30,6 +31,10 @@ A NativeScript plugin is any npm package, published or not, that exposes a nativ
3031

3132
The plugin must have the directory structure, described in the [Directory Structure](#directory-structure) section.
3233

34+
# Where Can You Find NativeScript Plugins
35+
36+
You can find a list of Telerik-verified NativeScript plugins on the [Telerik Verified Plugin Marketplace](http://plugins.telerik.com/nativescript), and a list of community-written NativeScript plugins by [searching for “nativescript” on npm](https://www.npmjs.com/search?q=nativescript).
37+
3338
## Create a Plugin
3439

3540
If the NativeScript framework does not expose a native API that you need, you can develop a plugin which exposes the required functionality. When you develop a plugin, keep in mind the following requirements.

0 commit comments

Comments
 (0)