Listen to a special audio message from Bill Roper to the Hive Workshop community (Bill is a former Vice President of Blizzard Entertainment, Producer, Designer, Musician, Voice Actor) 🔗Click here to hear his message!
- Works with maps in a map-as-directory mode
- Own package config format in JSON
- Install packages with dependencies from Github and Bitbucket
- Install Lua files directly from Github, Bitbucket or custom hosts in config
- File and directory watcher (war3map.lua, sources, config)
- Dependency version resolution
Module Manager Features
- Include custom user directories as advanced sources
- Right dependency order in the target file
- ES6-like imports and exports in the Lua script
- Really fast target builder on-the-go (C# watcher)
1. Install WLPM
2. Save your map as a directory (Save as... menu item)
3. Open any terminal window (press Win+R and enter "cmd")
4. enter cd <your map directory>
5. then enter wlpm - it shows all applicable commands
To initialize your package enter wlpm update. It will create wlpm-package.json and .wlpm directory with the dependencies. If you use git (mercurial/svn/...) add .wlpm to your ignore file (.gitignore).
To add new dependency enter wlpm install <package> <version>
If you don't want to use MM on the client (Lua) side you can disable it by adding a new option to your wlpm-package.json:
"insertModuleLoader": false
With this option MM just includes code of the dependencies without the MM
Executing a command after building
It's possible execute a terminal command when the building process finishes:
Code:
"afterBuild": "echo \"hello world\""
It works for root projects only.
Publishing Packages
If you want to publish your package folow these steps:
1. Create a git repository at Github or Bitbucket
2. Create wlpm-package.json in the repository root
3. Add the "dependencies" and "sources" parameters. Refer the full config example below.
4. (optional) add git tag to the repository
5. Now this is a WLPM package!
Full config example (wlpm-package.json)
Code:
{
"title": "WLPM - Demo Map Package", // (optional) your package or root project title
"author": "ScorpioT1000 / [email protected]", // (optional) author information
"license": "MIT", // (optional) source code license
"dependencies": { // list of packages and files required by your source code
// github repository from a master branch
"https://github.com/123/456": "*",
// github repository from the release tagged as "1.1.1"
"https://github.com/123/456": "1.1.1",
// bitbucket repository from the release tagged as "1.0.0" in an object format
"https://bitbucket.org/123/789": { "type": "package", "version": "1.0.0" },
// inserts a file directly from the repository
"https://github.com/123/456/blob/master/somefile.lua": {
"type": "file",
"topOrder": true // omit this option or set to false to insert the file after repositories' sources
}
},
// (optional for root project) where your sources are stored. It's important for the package, but can be omitted for root project (it watches "target")
"sources": [
"src"
],
// (optional) where to store compiled lua build. It works for root project only.
"target": "war3map.lua",
// (optional) execute this command after build, e.g. "echo \"Hello!\""
"afterBuild": "",
// (optional) set this to false if you want to replace built-in module manager by your own
"insertModuleLoader": true,
// (optional) allow more hosts for direct file dependency (allows github.com and bitbucket.org by default). It works for root project only.
"allowHosts": []
// (optional) set custom file extensions when building "sources"
"sourceExtensions": "*.lua"
}
Restrictions
1. It doesn't support partial version placeholders like 1.* because it doesn't use package registry
2. It performs full re-download on any config requirement change (planned to fix in the future)
3. No VSCode integration yet, but it's planned
For C# developers
You are free to fork and build your own modifications! My requirement is that any "author" fields in C# code are allowed to be supplemented only(!).
Seems a lot like NPM. That being said, wlpm is a pain to write.
I do not like writing version number either, I'd leave that as optional and get the latest by default.
Some feedback:
Need package initialization to set things like "sources" in the wlpm-package.json
Need to be able to use local packages. I would like to do some integration testing of RxW3 without pushing to github publicly
I would like to be able to compose packages, IE: Declare a piece of a package in another file like the operators section of RxW3
Need better documentation on what can go in the wlpm-package.json
Installing went fine. I'd prefer a portable executable that I would add to the system path myself, but I guess this might be easier for inexperienced users.
Trying to install your demo package 1.0 gave me an error:
Installing 1.1 does seem to work.
Trying to install packages with .git at the end of the URL will fail
Trying to install the package without the .git at the end will then also fail
If you then delete ".wlpm" and "wlpm-package.json" it will install fine again.
I also couldn't get the demo package working. It would install, but then if I tried to use it my map would no longer launch. You can find the map attached with the 2 demo lines in the map script header. I'm setting this to Awaiting Update for now.
Ok so I figured that you can't use the WE for scripting, but have to do it all directly in war3map.lua which isn't a big issue, but it would be nice if it was mentioned.
You also have to then run build after every time you save with the WE as it will overwrite your war3map.lua. Your feature lists says you have some kind of C# watcher in the Module Manager to do this automatically, but I don't see any .exes or .cs files in there. I'm also unsure why it is separate and not included with WLPM by default.
I also get this error when I paste your demo-hello example code in the war3map.lua, but I have it installed and it is listed in the wlpm-package.json as a dependency.
A step by step guide on installation and first package use with a paragraph on expected workflow would be really helpful.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.