sourcerer-io / awesome-libraries Goto Github PK

• Support libs for lua and your ecosystem!

One of the most popular GitHub repos is a game for Byond. I think this should make it a good candidate for being recognized by Sourcerer. The repo was featured on the GitHub Octoverse for having a ton of contributers.

Byond: http://www.byond.com/
Game: https://github.com/tgstation/tgstation

Perhaps we could break those out by language to reduce merge conflicts or create a specification and encode the values in the language json itself. Then have the spec check as part of the build that the language json and tags are valid.

Sadly, it's actually a good use-case for https://jsonnet.org/

I have a problem setting up my Dev environment with gradle and network issues with jcenter. Is it possible for a jar release, so I could directly run the jar file.

HCL is used by Terraform and Nomad

At the moment smartcontracts are shown as gray "unattributed".

Solidity smartcontracts code looks like javascipt file and start with
pragma solidity
also includes at least one declaration
contract

It "should" be easy to detect.

PHP is one of the most popular programming languages. It powers almost 80% of all websites.

There is a huge developer community and numerous libraries, frameworks, tools, etc. Adding even the most popular of these to the libs/php.json will take forever. And then maintaining the list will also require a huge effort.

I think there is a better and simpler way though. Most of the modern PHP projects use Composer dependency manager. Those that do, have composer.json file in the root of the repository. The structure of this file is very well known and documented.

composer.json usually provides all the necessary information about the project / repository, such as name, URL, type, license, class namespaces, dependencies, and so on. If support for Composer is added to Sourcerer, it will immediately expand the knowledge and understanding of the PHP repositories, without doing any manual work. And it'll be easier to keep things up-to-date too.

I think this can also be implemented as a more or less generic support for dependency management tools, as there are others (npm for Node.js, etc). Extracting this information from the project repositories is a lot easier, faster, and more reliable than maintaining the technology lists manually.

Hi, thank you very much for your wonderful project. I was looking forward to service as you provide.

I got an email from Sourcerer. The mail has the following message. I think sourcerer-io/libraries should be sourcerer-io/awesome-libraries because the link redirects to this repo.

(I don't know I should have reported this issue in this repo...)