Packaging jQuery Plugins: Difference between revisions
Jump to navigation
Jump to search
| Line 22: | Line 22: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
The `--save` parameter updates `package.json`, adding the package as a dependency of the project. | * The `--save` parameter updates `package.json`, adding the package as a dependency of the project. | ||
* To use a branch other than `master` append `#branchname` to the repo URL. | |||
* [http://blog.npmjs.org/post/112064849860/using-jquery-plugins-with-npm Using jQuery plugins with npm], `npm` Blog | * [http://blog.npmjs.org/post/112064849860/using-jquery-plugins-with-npm Using jQuery plugins with npm], `npm` Blog | ||
Revision as of 17:40, 8 April 2016
Overview
Process for creating, maintaining, and distributing jQuery plugins using GitHub and npm.
Helper tools
- jQuery Boilerplate Boilerplate for creating jQuery plugins
Distribution
Marking a release
Using plugins in projects
Use npm to fetch the plugin from GitHub, included in in the project, and add it to the project requirements:
$ npm install git+https://git@github.com/northrose/lightboxLink.git --save
- The
--saveparameter updatespackage.json, adding the package as a dependency of the project. - To use a branch other than
masterappend#branchnameto the repo URL.
- Using jQuery plugins with npm,
npmBlog - Publishing your jQuery plugin to npm, the quick and dirty way,
npmBlog
See also
Internal pages
References
<referemces />