Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

npm support #38

Open
ducin opened this issue Oct 6, 2015 · 5 comments
Open

npm support #38

ducin opened this issue Oct 6, 2015 · 5 comments
Milestone

Comments

@ducin
Copy link

ducin commented Oct 6, 2015

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.

@rom1504
Copy link

rom1504 commented 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 rom1504@c3f47e7

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

@infiniteluke
Copy link

@lbovet It seems to me a v2.0.0 could be in order since adding NPM support is a breaking change.

However, there are many other minor PRs not getting any love. I don't see much activity on this project, is there a roadmap of the project future?

@yanick yanick mentioned this issue Feb 13, 2018
@yanick
Copy link
Collaborator

yanick commented Feb 16, 2018

In the npm version, I think we need to make sure that docson works in 4 incarnations:

[ ] as a npm library (duh)
[ ] as a cli tool that spin off an express app (docson ./my/schema.json)
[ ] as a widget
[ ] as a Swagger add-on

@yanick yanick added this to the NPM migration milestone Feb 16, 2018
This was referenced Feb 16, 2018
@rom1504
Copy link

rom1504 commented Feb 16, 2018 via email

@yanick
Copy link
Collaborator

yanick commented 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. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants