Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

npm support

See original GitHub issue

How about adding docson to npm registry, so that non-bower developers may use docson?

Many people say that npm will replace bower soon (and bower will become useless), one may agree with it or not. Anyway, some users would appreciate publishing docson in npm.

Issue Analytics

State:
Created 8 years ago
Comments:5

Top GitHub Comments

1reaction

rom1504commented, Mar 22, 2016

I published a docson package there https://www.npmjs.com/package/docson

I removed some stuff so it make more sense as a package, so I’m not sure it makes sense to make a PR of that here.

I also added @lbovet to the package, if he wants to do anything about npm support for docson.

here is the branch where the changes are https://github.com/rom1504/docson/tree/npm and the important commit https://github.com/rom1504/docson/commit/c3f47e734f17d241123f42ac2c149f7831907eb0

In that form, it’s fully usable with browserify.

0reactions

yanickcommented, Feb 17, 2018

[branch is inspirational, not to be taken as-is] Yeah, I see it as such too. Mostly considering there have been a few clashing code changes since then too. But it does provide a good gist on which to base the process. 👍