I’m speaking about issues like:
– JSON learn/write libraries
– Threat administration and place sizing helpers
– GUI / chart part libraries
– Sample recognition utilities (candlestick, indicators, and so on.)
– Value motion / SMC / orderflow tooling
– Every other reusable MQL library you’ve constructed in your personal work
I’ve been engaged on KnitPkg (https://knitpkg.dev), a contemporary, Git‑first package deal and challenge supervisor for MQL4/MQL5 that brings an npm-like workflow to MetaTrader: semantic versioning, reproducible installs, and a registry of packages backed by Git repositories.
Now that KnitPkg is launching, I’d like to assist different builders publish their very own libraries into this ecosystem.
The way to share your MQL code by way of KnitPkg
When you have an MQL library you’re prepared to share, the fundamental concept is:
1. Create a Git repository together with your code on any supported host: MQL5Forge, GitHub, GitLab, Bitbucket
2. Observe the “Creating Packages” information within the KnitPkg docs to see the construction and ideas:
https://docs.knitpkg.dev/user-guide/creating-packages/
You don’t must get every part good on the primary strive. To make this simpler throughout the launch section of KnitPkg, I’m providing hands-on assist.
MY OFFER: I’LL ADAPT YOUR REPO TO THE KNITPKG STRUCTURE
To encourage extra excessive‑high quality packages within the registry, right here’s how I may help you, step-by-step:
1. You create the Git repo on any supported host (MQL5Forge, GitHub, GitLab, or Bitbucket) and push your present MQL code there.
2. You ship me a non-public message on MQL5 with the repository URL and a brief word that you simply’d prefer it tailored for KnitPkg.
3. I’ll fork your repository, modify the construction and manifest to match the advisable KnitPkg challenge structure, and open a Pull Request with the adjustments.
4. You assessment and merge the Pull Request into your repository.
5. With the construction in place, you publish your challenge to the KnitPkg registry by working this single command in your machine: ‘kp register’. After that, your package deal turns into installable by any developer utilizing KnitPkg, by way of a easy:
$ kp add @yourorg/yourpackage
$ kp set up
Discoverability: your code within the KnitPkg Net Registry
As soon as your repository is revealed within the KnitPkg registry, your package deal might be simply searchable by the online interface:
For MQL5 initiatives: https://registry.knitpkg.dev/mql5
For MQL4 initiatives: https://registry.knitpkg.dev/mql4
Different builders will be capable to uncover your work by group, package deal identify, creator, license, or challenge sort, and set up it instantly into their very own MetaTrader initiatives.
Why this issues
MetaTrader initiatives typically develop by copy/paste and advert‑hoc folder sharing. By turning your libraries into versioned packages:
– Different merchants and builders can reuse your work reliably.
– You acquire a transparent distribution and replace channel in your code.
– The MQL group strikes towards trendy, reproducible workflows, just like what JavaScript, Python, and others already get pleasure from.
In case you’re , simply ship me a non-public message together with your repo hyperlink and I’ll enable you to deliver your library into the KnitPkg ecosystem.
Let’s make MQL growth extra modular, shareable, {and professional}—collectively.