I have experience in a niche field with some sort of DSL which is an interpreted, scripting language.
The eternal question arises about packaging up libraries of reusable code, eg just for example, if we want to build a few apps with some common logging library, we want to package some scripts related to logging stuff to make a library, have it versioned, probably uploaded into a repository somewhere, etc. Then our apps need a config or whatever to say pick this logging lib version x, put it somewhere and then we can load and use it. Ideally we build a versioned app with versioned dependencies and it is also bundled and put to a repository for deployment.
I have seen solutions to this totally in house built based off maven, it's good in many ways and it solves the problem, we can control many things, hook in our unit tests etc etc. But maven is also very complicated, not least when you are really building something quite customised from the ground up which is my feeling here.
I have also done a solution with npm, it is way simpler, maybe too simple, you have to live with a node_modules folder for example, you can still get your unit tests plugged in and run npm test so it's basically good though.
I am considering other solutions to this problem and wanted to sound out ideas here. The main problem is the niche where this DSL lives is really not modern in many respects, many users are not even unit testing, some not using source control, don't understand why libraries are good etc. Many in this space will reject out of hand a complex solution. maven is quite good in my eyes but it's a super hard sell. npm is okay but still people may be put off because why are we using a javascript technology here, it feels off somehow.
Anyway thanks for reading this far and let me know if you have any opinions about that.