Feature: add support for local path dependencies

[itsfrank]

pesde currently offers a great selection of ways to consume dependencies; however, the ability to consume pesde packages from the local files system is missing.

Two other package managers I use frequently: Cargo, Lazy.nvim, offer this and it's really great when you are the consumer of a package you maintain.

Examples

Cargo

[dependencies]
my_dep = { path = "~/dev/my_dep" }

Lazy.nvim

return {
    dir = "~/dev/my_dep",
    config = function() ... end
}

Use-Case

A common occurrence as a package maintainer is the following:

• Create a package and distribute it with a package manager
• In a different project, consume said package with the package manager
• Discover an issue in the package through the use of it in a downstream project

In this scenario, what you want is the ability to iterate on the package in a branch of the main repo on your system, and consume the local changes with as little friction as possible on the downstream project where the issue reproduction is present.

Cargo achieves this by checking and rebuilding path dependencies on change, Lazy gets this for "free" via Lua's dynamic nature.

It would be wonderful if a similar workflow were possible with pesde.

Additional benefit

An additional benefit would be to make it easier to test the pesde configuration of a package before even making a commit. Currently, the only way to test if a package is correctly configured is to push to git and consume from the git revision; the iteration flow for this is a bit unfortunate:

• Make a change
• Push
• Copy revision hash
• Paste revision hash in test consumer's pesde.toml
• pesde install
• Test & repeat

With local path dependency declaration, this could be cut down to:

• Declare dep & pesde install (one-time)
• Make a change
• Test & repeat

[daimond113]

Thanks for the issue! This will be fixed (added) in pesde 0.6.