Download pdf - Become a node package maintainer

become a node package maintainer

opinionated guide about creating and maintaining

Donnerstag, 22. November 12

intro


whois damienklinnert.com

• javascript developer && computer science student && working at doctape

• follow me @damienklinnert


mailto:[email protected]

mailto:[email protected]

summary

one: create

• npm commands, package.json, folder structure, documentation, testing, style, build tools, git(-hub), publish

two: maintain

• evolution / revolution, update, semantic versioning, appreciate help


y u speak?

• node and npm are awesome

• everyone can publish packages w/o control

• lots of crappy packages (crappy maintenance, crappy docs, crappy code, crappy style, crappy structure, …)


one: create


npm commands• npm init

• npm install

• npm run-script

• npm docs

• npm test

• npm pack

• npm adduser

• npm publish


package.jsoncreate skeleton with $ npm init


folder structure


documentation

• minimum: README.md and LICENSE

• better: docs/, HISTORY.md, config.example

• use comments, jsdoc and UML

• easy to install, use and contribute


testing

• use all: unit tests, functional tests, integration tests

• add working examples in examples/

• travis-ci

• utilize $ npm test


style

• lint your code (use a lintconfig and ship it)

• use only one coding style and keep a reference to it

• make it simple + understandable


build toolGRUNT.JS

simple tasks: npm, complex task: grunt.jsDonnerstag, 22. November 12

git(-hub)

• .npmignore / .gitignore

• specify repo and bugtracker url in package.json

• keep versions the same with git tags

• create HISTORY.md from git log


publish

• as easy as $ npm adduser && npm publish

• will read your package.json


two: maintain


evolution / revolution

• check whether there already is a similar package and contribute instead

• stick to your own design, style and guides


update

• update often

• fix bugs ASAP

• never ever unpublish (be aware of dependencies)

• keep repo and npm packages at the same state


semantic versioning

MAJOR.MINOR.PATCH

0.1.0, 0.2.3, 2.3.15Major: API changes

Minor: new functionalityPatch: bugfixes

http://semver.org/


http://semver.org/

http://semver.org/

appreciate help

• name contributors

• react immediately

• enable discussions

• merge pull requests


thank youwho writes a tool to automate this?
