npm install --save git+https://github.com/wizardsoftheweb/modifies-root-package
npm tTODO: write documentation after the API is done
Polluting the global namespace is generally considered a bad idea, so why would you do it on NPM?
These percentages are pretty arbitrary. Today's 47% could be tomorrow's 90% or vice versa.
Once all of these are finished, I'll release v1. Until then, v0 should be used with caution, because it's not stable.
| Progess | Feature |
|---|---|
| 0% | Define abstract superclass |
| 0% | Decide on and define concrete API |
| 0% | Create decorator (needs research) |
| 0% | Create bin scripts to build publishable packages |
| 0% | Set up index properly |
| 0% | Export the full namespace |
| 0% | Compile declaration file |
| 0% | Compile docs from source |
| 0% | Incorporate @todos somewhere prominent in the docs |
| 0% | Publish package on npm |
These are things I'd like to add, but probably won't be included in v1. If not, they'll most likely constitute one or more minor version increments.
| Progess | Feature |
|---|---|
| 0% | Greenkeeper (or similar) integration |