Is Node Swagger still being actively developed?

[sunsus]

I can not see a lot of commits in the last months and there are a lot of old and insecure dependencies used.
Even the build is marked as faild.

Thats the reason for this Question.

If it's not anymore actvily developed thats fine for me but we have to switch to an other library.

[MnHung]

I have the same question.

Some facts:

• Swagger release OpenAPI 3.0 https://swagger.io/blog/news/announcing-openapi-3-0/ a year ago ( July 26, 2017 )
• Swagger Editor is now at version 3.6.8, supports OpenAPI 3.0
• Swagger node depends on "swagger-editor": "^2.9.2", support OpenAPI 2.0

[SirBif]

I also see passing PRs still left unanswered and unmerged. Is anyone still maintaining this?

[cognivator]

How does one start maintaining this repo?

Or is this a signal that the community is using something else for REST dev in node?

FWIW, graphQL is not a replacement for REST apis, so I hope the node ecosystem doesn't lose all REST libs.

[bestekov]

+1

[DavidBiesack]

I also asked about updates or workarounds (notably for swagger project edit) on the Swagger group; see https://groups.google.com/forum/#!topic/swagger-swaggersocket/M6rSB8f7iAU

[muxator]

Same problem here. Any infos?

[chezearth]

I really like this library; it makes building APIs with quick and easy while not being too opinionated or limiting options. I am having a go at updating dependencies and fixing the code base to keep it working on Node versions >= 6 (--is that far back enough?). You can help me and this is my fork. I would love to get it to work with OpenAPI/Swagger 3.0 as that is a much better spec, too. I can't find any alternative that has up to date dependencies and works with OpenAPI 3.0 and is as easy and convenient as this project, except maybe for LoopBack. I know there are good up-to-date tools like swagger-express-middleware, etc. -- maybe we can build on those?

[timaschew]

Looks like the community needs to fork it and maintain it.
From the graph this seems to be the most maintained fork: https://github.com/chezearth/swagger-node

@webron @shockey @fehguy
Can you please pin this issue so that people are aware of this issue before they create new issues.

[DeeDeeG]

If we get a community fork going, a good place to start might be to get Travis CI tests passing. Anyone have any success with that? (My second priority would be addressing npm audit results.)

[chezearth]

I'm in support of getting a community fork going. I agree that the best approach is to get Travis passing first. Then to address the npm audit issues. Then, I'd like to see it become compatible with Swagger/OpenAPI 3, which may happen automatically as the npm audit and dependency issues are fixed with newer Swagger libraries

[maziyarpanahi]

I did my best to update the tests and every dependencies I could without breaking anything.

I have Swagger in production and I know there might be other libs that I can replace it with, however I'd prefer not to do this at the time. I do my best to keep these 3 repositories as up to date as possible since my application relies on them: (they all at 0.8.0 version)

https://github.com/multivacplatform/swagger-node
https://github.com/multivacplatform/swagger-express
https://github.com/multivacplatform/swagger-node-runner

[timaschew]

Actually it would be better to get permission for this repo for volunteers instead of a fork.

But that requires some actions from other people.
Please give use some feedback: @webron @shockey @hrldcpr @fehguy @micmro @klammm @meisterlampe

Alternatively if the swagger-api organization don't want this, we could create a new community-driven organization and transfer this repo to it.

[maziyarpanahi]

I would love some permissions to contribute! Most of the repositories I contribute to allowed me to do so as a member which I am really grateful. For my use, those 3 repositories, I have reported issues, I made pull requests for those issues, I even emailed one or two authors if I remember correctly.
I wasn't lucky to get any response, but I would be very happy to see some permissions going to some active users/contributors here or a new community. (anyway to keep these repos alive and up to date is beneficiary to me and others)

[webron]

Hi everyone - sorry for the radio silence for so long. It's very exciting to see such commitment and devotion from the community and it should not go unheard. You deserve better, and hopefully we can make it happen!

As you figured out by now, the state of the project is somewhat in a limbo.

With that said, I'll be happy to open for discussion what can and should be done with the project. We've had some ideas ourselves, but not enough steam to move forward. With people like you, we may just be able to make it happen.

To get this process started, please start by adding in comments: PRs/Issues that you feel should be be addressed in a pressing matter, ideas/suggestions you have about where this project to be headed, and if you want to help out, please mention at what capacity.

I imagine some of you are angry with what happened so far (and I don't blame you), but I ask that we keep the conversation in a positive manner and try to make real progress.

[jcferrer]

My team has been working for almost three years now with the original a127 project that preceded this effort and haven’t been able to migrate to swagger-node due to multiple issues that have not been resolved. I am glad there is still interest to make progress. Let me know how I can help.

[DeeDeeG]

Would love to have dependencies updated, to help address npm audit results. (As @makuro did in a fork, I think mocha can go to devdependencies. See: makuro@9045d25e69710bf5)

My second priority would be having Travis CI passing. Just to help with future PRs being easier to review.

I'm afraid I'm not so good with programming, so I am unlikely to be able to help with these too directly. But I can cheer on those who do it!

Thank you for your response @webron!

P.S. The fork by @maziyarpanahi (https://github.com/multivacplatform/swagger-node) looks like a fine start toward those two priorities I mentioned.

[webron]

Regarding the build process - in the past few months we've migrated the majority of our projects from Travis CI to our own instance of Jenkins. It's publicly accessible, everyone can see the builds (open source, after all), but it's easier for us to maintain, make sure it's performant and have regular backups. We'd be happy to take a look into migrating the build there and improve the process over time (you can take a look at the work we've done with swagger-ui and swagger-editor regarding the build process).

[DeeDeeG]

Jenkins sounds okay! I notice it gives the green check / red x here on GitHub, so it's easy to tell at a glance if tests pass and if the build succeeds. And folks can click through to review the build log and review any errors. That's all I could ask for, so the specific CI provider isn't a big deal in and of itself. Whatever works should be okay, IMO!

[maziyarpanahi]

Hi @webron, I would love to have some permission for these 3 repositories especially the last two since I have updated them to the lasted version to work with new Sway 2.x:

• swagger-node
• swagger-express
• swagger-node-runner

As soon as I have some permissions to merge pull requests and publish on NPM, I would update to the latest changes from my own repositories and remove the ones I have. (I would like to keep these 3 updated rather than my own since there are more users here to help/review).

Many thanks

[webron]

@maziyarpanahi - only swagger-node is out project. swagger-express and swagger-node-runner are not ours, so we can't help with modifications to either.

[DeeDeeG]

Hi. Sorry to resurrect this issue again...

I can't tell if everyone who wants to make changes to this repo wants to make the same changes... but I think we can all agree it would be nice to see forward movement.

Can someone with ownership / commit access to this repository perhaps schedule a time to move a few to-do items forward, and/or plan to publish an updated package to NPM? Or indicate that a few targeted PRs would be welcome and likely to be reviewed, in order to make the repo current again?

Or would owners/admins of this repo be interested in adding some outside collaborators with commit access, to be new/additional maintainers?

(And if not, it would probably helpful to indicate more definitively that the project is not maintained at this repo, to provide clarity before a main community fork would be established. I assume people mainly want to know where to put their work before they start posting it.)

Not trying to be annoying, but just hoping to see a good resolution, or a clearer way forward.

Thanks again.

[camsjams]

Since I've looked at this thread more than once, I figured I would help future people out, please see:
How to migrate a Node JS Express project out of Swagger-Express

Note: I am not associated with either project but just wanted to share a migration guide.

[itai421]

Any news?
I think this is a great project, and would be happy to help out