-
Notifications
You must be signed in to change notification settings - Fork 96
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
Comments
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. |
@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? |
In the npm version, I think we need to make sure that docson works in 4 incarnations: [ ] as a npm library (duh) |
Yes I agree. I did it a long time ago but I believe I remember my branch
only does the first point, I removed a bunch of files which are actually
probably needed for the other points. So I think that branch is more in the
"ideas" area than in something that should be a direct PR.
…On Fri, Feb 16, 2018, 21:04 Yanick Champoux ***@***.***> wrote:
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
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#38 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ACPN_j0QIoLAi8lEoh8JU2YP_GZu45QOks5tVd9QgaJpZM4GJv-q>
.
|
[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. 👍 |
How about adding
docson
to npm registry, so that non-bower developers may use docson?Many people say that
npm
will replacebower
soon (and bower will become useless), one may agree with it or not. Anyway, some users would appreciate publishingdocson
in npm.The text was updated successfully, but these errors were encountered: