-
Notifications
You must be signed in to change notification settings - Fork 30
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
Use npm dependency instead op github link #16
Comments
btw, I can make a PR if you want, just gimme a sign |
And the 1.4.1 includes bugs they fixed in their v2 but don't want to fix in their v1. That's the purpose of my fork, 2 commits fixing some issues while fetching a swagger file over internet https://github.com/zallek/json-schema-ref-parser/commits/ |
ok, I get the problem. Will ask the guys from swagger-parser to update their libs in that case. Maybe I can help out there :-) |
yeh if you can, would be great :) |
@Remco75 Did you ever end up asking the guys from swagger-parser? Can't find an open issue about it. |
@Remco75 @picodealion any news? |
It looks like the latest version of If you are still working on the tool and are able to get rid of the github dependency, that'd be awesome! Great looking tool! |
In the package.json you use the following link:
"json-schema-ref-parser": "github:zallek/json-schema-ref-parser#v1",
To a very old version of your own module.
Could you just link to the regular release on npm?
Reason: my compagny's build system uses an internal npm-repo, and can't handle the external github links... :-(
would be great if you could fix this
The text was updated successfully, but these errors were encountered: