When you have a dependency which depends on a version of an engine which is not compatible with the version of that engine configured with your project, a warning is displayed, making version incompatibility issues easy to catch.

This means that you no longer need to bring your own lune installation, and just installing pesde should be enough to start writing code!

But that's not all, folks!

For a more comprehensive list of changes, consider reading the release changelog: github.com/pesde-pkg/pe...

Similarly, deprecation allows you to disallow entire packages from being depend on, displaying a warning on the package's page.

It is now also possible to yank and deprecate. Yanking is a version specific operation which marks a specific version of your package as unresolvable, unless someone already explicitly depends on it in their lockfile. This is useful if you accidentally publish a broken version of your package.

In order to make pesde's already disk-efficient caching even more convenient, pesde now has the ability to prune its CAS store from the CLI. Run `pesde cas prune` to remove unused packages from the CAS and claim back your disk space!

We include some more useful utility commands for dependency management now -- namely, `list` to list all dependencies and `remove` to remove a dependency from the manifest.

We have fully rewritten the installation experience, with improved and ✨pretty✨ outputs. But that's not all! Installs are incremental now, meaning pesde does not attempt to install all dependencies from scratch, and only installs those which have had changes.

Slight wording correction: scripts packages are a way to export scripts as packages so they can be used as dependencies by other people.

Not all scripts modify the behavior of pesde, only some specific ones (only 2 at the time of writing) do. The docs mention this.

Read the docs: docs.pesde.dev/guides/scrip...