@@ -36,10 +36,11 @@ changes to the version.
36
36
37
37
The name is what your thing is called. Some tips:
38
38
39
- * Don't put "js" or "jquery" in the name. It's assumed that it's js, since you're
40
- writing a package.json file, and it's assumed that it's a jQuery plugin, because
41
- you're registering it on the jQuery Plugins Site. Additionally, you will be listing
42
- ` jquery ` as a dependency, along with compatible versions (see 'Dependencies' below).
39
+ * Don't put "js" in the name. It's assumed that it's js, since you're
40
+ writing a package.json file.
41
+ * Do put "jquery" in the name. This may seem like the opposite advice from the previous
42
+ tip, but this is important for projects loading jQuery plugins and non-jQuery plugins
43
+ through a module loader.
43
44
* The name ends up being part of a URL. Any name with non-url-safe characters will
44
45
be rejected. Also, it can't start with a dot or an underscore. The jQuery Plugins
45
46
Site is UTF-8.
@@ -48,7 +49,7 @@ The name is what your thing is called. Some tips:
48
49
to see if there's something by that name already, before you get too attached to it.
49
50
* If you have a plugin with the same name as a plugin already in the jQuery Plugins
50
51
Site, either consider renaming your plugin or namespace it. For example, jQuery UI
51
- plugins are listed with the "ui- " prefix (e.g. ui- dialog, ui- autocomplete).
52
+ plugins are listed with the "jquery.ui. " prefix (e.g. jquery.ui. dialog, jquery.ui. autocomplete).
52
53
53
54
## <a name =" field-version " >version</a >
54
55
@@ -219,7 +220,7 @@ digits after the first "x" are ignored.
219
220
220
221
``` json
221
222
{
222
- "name" : " color" ,
223
+ "name" : " jquery. color" ,
223
224
"version" : " 2.0.0b1" ,
224
225
"title" : " jQuery.Color()" ,
225
226
"author" : {
0 commit comments