~sbaildon/next-ls

251d7b8c — github-actions[bot] 21 days ago
chore(main): release 0.21.2 (#453)
fix(runtime): correctly set MIX_HOME in runtime (#452)
chore(nix): update deps hash

refs

main
browse  log 

clone

read-only
https://git.sr.ht/~sbaildon/next-ls
read/write
git@git.sr.ht:~sbaildon/next-ls

You can also use your local clone with git send-email.

#Next LS

Documentation GitHub release (latest by SemVer including pre-releases) GitHub all releases GitHub Discussions Discord

The language server for Elixir that just works. 😎

Still in heavy development, but early adopters are encouraged!

Please see the docs to get started.

#Sponsors

Next LS and elixir-tools are sponsored by a ton of amazing people and companies. I urge you to sponsor if you'd like to see the projects reach their maximum potential 🚀.

https://github.com/sponsors/mhanberg

#Platinum + Gold Tier

José Valim

#Remaining tiers

Christopher GraingerMikkel HøghEthan GundersonSebastian HenaoAlexander KoutmosSimon WolfParker SelbertNoah BetzenShannon SelbertDorian KarterAndré Luiz da Fonsêca Paesjackson millsapsLeon QadirieDamir VandicEric OestrichBrett WiseDavid BernheiselDavid BaldwinQdentityNFIBrokerageRudolf ManusadzhianClark Lindsayv1d3rm3Stephen BusseySuperedKeith GautreauxJean-Luc GeeringJonathan YankovichJamie WrightZach NorrisJoe MartinezMarcøsDan DresselhausMarcel FahleMichael KummAmplifiedThibaut BarrèreVictor RodriguesDave Lucia0x7fMarcelo Dominguez

#Development

# install deps
mix deps.get

# start the local server for development in TCP mode
# see editor extension docs for information on how to connect to a server in TCP mode
bin/start --port 9000

# run the tests
mix test

#Production release

Executables are output to ./burrito_out.

# produces executables for all the targets specified in the `mix.exs` file
MIX_ENV=prod mix release

# produce an executable for a single target
BURRITO_TARGET=linux_amd64 MIX_ENV=prod mix release

#Contributing

This project follows Conventional Commits and will "Squash and Merge" pull requests.

This means that you don't necessarily need to write your actual commit messages with Conventional Commits, but the Pull Request title needs to, as it is used as the commit title when squashing and merging. There is a CI check to enforce this.

Conventional Commits are required to use Release Please, which is used to automate the changelog, release, and building/publishing executables.