-
Notifications
You must be signed in to change notification settings - Fork 28
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 install fails #10
Comments
Thank for your report. I have pushed a commit to solve it. Please try to reinstall
|
Not working yet... have you published it to npm? |
And another issue. I'm using 1.3.4 now. The /docs route works well, but when I access the app in it's default port e.g. http://localhost:3000 then I'm redirected to http://localhost:3000/s?url=/docs but receiving 404 Not Found. |
I think you should use the latest version. In case swagger site does not work, you can use link http://petstore.swagger.io/?url=http://localhost:3000/docs |
Yeah but I want to be able to serve the UI by myself and not depend on external swagger.io. |
Did you try Installation & Run from Source Code? |
No I haven't... why would I run from source code? :P |
I removed "install and run via NPM". Actually, Swagger Combined should run as an independent service. |
Would swagger-ui work in that way? Why cant the module just be configured dynamically (without a static .json file which is not so scalable way to configure modules), and then supply methods to get the final combined json? That's more modular, instead of forcing the clients to use the module as an external service for some reason.. |
Installing the module in a fresh Sails.js project and getting the following error:
The text was updated successfully, but these errors were encountered: