vlang/awesome-v

A curated list of awesome V frameworks, libraries, software and resources.

awesome-v's Issues

Add Gitly and vlang/pdf

Hi

Just wondering why those are not on the list:

• Gitly https://gitly.org/
• vlang/pdf https://github.com/vlang/pdf

linter broken

The CI linter is broken

npm WARN exec The following package was not found and will be installed: [email protected]
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=18' },
npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '^18.19.0 || >=20.5.0' },
npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=18' },
npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=18' },
npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=18' },
npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=18' },
npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@sindresorhus/[email protected]',
npm WARN EBADENGINE   required: { node: '>=18' },
npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=18' },
npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=18' },
npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=18.18.0' },
npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=18' },
npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=18' },
npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=18' },
npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=18' },
npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=18' },
npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@sindresorhus/[email protected]',
npm WARN EBADENGINE   required: { node: '>=18' },
npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=18' },
npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=18' },
npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=18' },
npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=18' },
npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=18' },
npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=18' },
npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=18' },
npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=18' },
npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
npm WARN EBADENGINE }
npm WARN deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm WARN deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm WARN deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
file:///home/runner/.npm/_npx/b4a07bb0d9034d53/node_modules/execa/lib/utils/max-listeners.js:1
import {addAbortListener} from 'node:events';
        ^^^^^^^^^^^^^^^^
SyntaxError: The requested module 'node:events' does not provide an export named 'addAbortListener'
    at ModuleJob._instantiate (node:internal/modules/esm/module_job:123:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:189:5)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:530:24)
    at async loadESM (node:internal/process/esm_loader:91:5)
    at async handleMainPromise (node:internal/modules/run_main:65:12)

Articles

An Introduction to V

This article was written back in 2019 and really does not belong here anymore. It mentions many faults which have been corrected since the article was written. It does not reflect well of the Vlang team.

Thanks
Jim Richards

Alphabetize

Just a reminder for sometime when anyone has time: we should probably alphabetize lists for fairness perception and maintain such.

Where can I find companies to work with vlang?

Hi @vlang, how are you?

Where can I find companies to work with vlang?

Following awesome guidelines

I noticed @Delta456 opened a PR in sindresorhus/awesome to add this repo to the main list.

Unfortunately, this list does not follow awesome guidelines:

• Should have license file (#50)
• Should have contributing guidelines (#47)
• Should pass awesome linter (#47)
• Should have awesome and awesome-list topics

Until we fix these issues, the awesome-v won't be added. But, anyway, following guidelines is always the best option.

Optional TODO:

• Update repo description to be equal to description in README.md

- A curated list of awesome V frameworks, libraries and software
+ A curated list of awesome V frameworks, libraries, software and resources.

Add awesome tag in README.md

Add the 'Awesome' tag that points to this

Alphabetize again

Noticed that there are a lot of items that are not in alphabetical order. Wondering if we should do a complete rearrangement.

This may reduce the confusion for contributors and avoid unnecessary repeated revisions (there is no requirement for alphabetical order in the Contribution Guidelines).

If you want, I'll create a pull request with the rearrangement done like what have been done in #151, and add this requirement to the Contribution Guidelines.

heroku-buildpack

The URL no longer exists. Please change the URL to the most recent fork:
https://github.com/zztkm/heroku-buildpack-v

vpm (v package manager)

https://github.com/yue-best-practices/vpm

Add pdf library

This is a simple PDF library.

https://github.com/vlang/pdf

Could be put in Text or Graphics.
Or get its own section.

Problems With Content

Articles - The Book of V

This repository or what I would call garbage does not belong in the awesome V list. The repository was setup over 2 years ago and rheir has been no activity. The supposed three chapters that were written are just copied and pasted from some rust material. I ask you please to remove this as it does not reflect well of the Vlang team.

Thank You
Jim Richards

The url for [RustemB/rosetta-code-v] is wrong

[RustemB/rosetta-code-v](https://github.com/ShellBear/v-regex) -- Solutions for Rosetta Code in V.

https://github.com/RustemB/rosetta-code-v This is the correct url

IntelliJ V dosn't exist anymore

The Github repository for the IntelliJ V plugin was removed. It seems like development was halted some time ago.

I suggest removing it from this list as the plugin isn't available anymore.

"Isaiah's UI" missing in the list

"Isaiah's UI" should be there in the "user interface toolkit" section :
https://github.com/isaiahpatton/ui

and probably also the tools he develop with his UI toolkit, in corresponding sections..

Neither vpm or vpkg build at the moment

I downloaded the git release, there's syntax errors with both package managers.

How to suggest additions?

I've developed the following native V-lang libs. Feel free to add them to your list

• A yaml parser: https://github.com/jdonnerstag/vlang-yaml
• A Rosie RPL parser: https://github.com/jdonnerstag/vlang-rosie

They are both not battle tested, but have a reasonable amount of test cases.

We implemented another V-like language with V.

vlang/website#23
The V language is awesome! In order to port it to the Mono virtual machine. We implemented another V-like language with V. However, due to limited time, we have to rely on Rust and C#.

vlang/v#638
vlang/v#709

We will guarantee that it will be open source after the beta and will donate to the V language after we have more income.