# What exactly does haxelib dev do? **URL:** \ **Category:** Haxe\ **Tags:** haxelib\ **Created:** [July 27, 2019, 11:02pm UTC](https://community.haxe.org/t/what-exactly-does-haxelib-dev-do/1935 "2019-07-27T23:02:29Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![uvtc](https://community.haxe.org/user_avatar/community.haxe.org/uvtc/32/1198_2.png) [@uvtc](https://community.haxe.org/u/uvtc)\ **Post date:** [July 27, 2019, 11:02pm UTC](https://community.haxe.org/t/what-exactly-does-haxelib-dev-do/1935/1 "2019-07-27T23:02:29Z")
What exactly does the `haxelib dev` command do? I’m looking at its docs [Using Haxelib - Haxelib Documentation](https://lib.haxe.org/documentation/using-haxelib/#dev) but still not understanding. Under what circumstances would I want to use `haxelib dev`? Thanks! ---
**Author:** ![joshtynjala](https://community.haxe.org/user_avatar/community.haxe.org/joshtynjala/32/792_2.png) [@joshtynjala](https://community.haxe.org/u/joshtynjala)\ **Post date:** [July 28, 2019, 2:42am UTC](https://community.haxe.org/t/what-exactly-does-haxelib-dev-do/1935/2 "2019-07-28T02:42:28Z")
It’s like installing a library from your hard drive instead of the internet. It’s often used for working with a library’s newest code that hasn’t been released yet. For instance, if a library author fixes a bug, you can use the latest code before they publish it. Or you could check out a library from GitHub and then make some tweaks (like add a new feature or whatever) and test your changes locally. ---
**Author:** ![ablum](https://community.haxe.org/user_avatar/community.haxe.org/ablum/32/415_2.png) [@ablum](https://community.haxe.org/u/ablum)\ **Post date:** [July 28, 2019, 9:33am UTC](https://community.haxe.org/t/what-exactly-does-haxelib-dev-do/1935/3 "2019-07-28T09:33:37Z")
With `haxelib dev` you can add a library that sits outside of haxelib’s folder structure. Typically used for developing your own libraries. When writing a library, you most likely also have at least one test or demo project that uses your library. Which you usually want to test against your most current dev version, and `haxelib dev` helps you do that. You might not even need a `haxelib.json` file for your (unreleased) library, if you point it to your `src` folder (or whereever you keep your sources). ---
**Author:** ![Gama11](https://community.haxe.org/user_avatar/community.haxe.org/gama11/32/7_2.png) [@Gama11](https://community.haxe.org/u/Gama11)\ **Post date:** [July 28, 2019, 10:21am UTC](https://community.haxe.org/t/what-exactly-does-haxelib-dev-do/1935/4 "2019-07-28T10:21:07Z")
> Or you could check out a library from GitHub […] It’s worth noting that `haxelib git` also allows you to do that, with less steps - it’s basically equivalent to doing a `git clone` + `haxelib dev`. The latter does give you more flexibility though, as it allows you to choose where to clone the library. ---
**Author:** ![uvtc](https://community.haxe.org/user_avatar/community.haxe.org/uvtc/32/1198_2.png) [@uvtc](https://community.haxe.org/u/uvtc)\ **Post date:** [August 1, 2019, 5:20am UTC](https://community.haxe.org/t/what-exactly-does-haxelib-dev-do/1935/5 "2019-08-01T05:20:20Z")
Sorry for the delayed reply. Ah! Ok, so, `haxelib dev` allows me to make it appear as if a library/project directory on my system is “installed” just as if it were a regular haxelib-installed library. Useful for when you’re developing a library which is not yet available on haxelib, but which you’d like to have available to programs on your system just as if the library were installed from haxelib. Thank you! ---
**Author:** ![joshtynjala](https://community.haxe.org/user_avatar/community.haxe.org/joshtynjala/32/792_2.png) [@joshtynjala](https://community.haxe.org/u/joshtynjala)\ **Post date:** [August 1, 2019, 2:10pm UTC](https://community.haxe.org/t/what-exactly-does-haxelib-dev-do/1935/6 "2019-08-01T14:10:12Z")
Just wanted to say thanks for pointing out `haxelib git`! It made my installation instructions for Feathers UI so much simpler. It also automatically installs dependencies, unlike `haxelib dev`, so it’s much closer to `haxelib install`. ---
**Author:** ![nanjizal](https://community.haxe.org/user_avatar/community.haxe.org/nanjizal/32/239_2.png) [@nanjizal](https://community.haxe.org/u/nanjizal)\ **Post date:** [July 18, 2020, 1:31pm UTC](https://community.haxe.org/t/what-exactly-does-haxelib-dev-do/1935/7 "2020-07-18T13:31:59Z")
I tend to find haxelib git more useful, since it installs the .git file you can make local changes in the haxelib and commit them, so totally agree with Joshtynjala.