scoped packages tip

readme.md

Typical process:

• fork a repo
• make your patch
• send PR

Sometimes its a long wait, and in the mean time you end up depending on Git (bad for semver/persistence, slow installs, etc).

public scoped packages

Alternatively, publish a scoped package until the original package catches up.

Branch off your PR, then rename the package name and bump semver accordingly.

{
  "name": "@mattdesl/browser-unpack",
  "version": "1.0.3",
  ...
}

Commit your changes and publish the scoped package:

npm publish --access=public

Now, in your app:

npm install @mattdesl/browser-unpack --save

And then:

var unpack = require('@mattdesl/browser-unpack')

(Maybe source transforms could transparently add scope to flagged modules to avoid having to change your codebase.)