Skip to content

Make in-house package management the default package management backend

Shubham Kumar requested to merge shubham/update-esy-to-legacy into dev

Motivation and Context

The idea is to deprecate the esy backend for package management and therefore remove the --package-mangement-alpha flag. This means if your projects require esy you need to add --legacy-package-management as a flag to make your packages/libraries compatible with ligo v1



  • compiler
  • website
  • webide
  • vscode-plugin
  • debugger

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Performance improvement (non-breaking change that improves performance)
  • None (change with no changelog)


  • Package management backend no longer uses esy by default. Using esy is now opt-in and requires --legacy-package-management option


  • If a new syntax has been introduced, put a message on slack ligo-lsp
  • Changes follow the existing coding style (use dune @fmt to check).
  • Tests for the changes have been added (for bug fixes / feature).
  • Documentation has been updated.
  • Changelog description has been added (if appropriate).
  • Start titles under ## Changelog section with #### (if appropriate).
  • There is no image or uploaded file in changelog
  • Examples in changed behaviour have been added to the changelog (for breaking change / feature).
Edited by prometheansacrifice

Merge request reports