https://github.com/elixir-tools/next-ls
The language server for Elixir that just works. Ready for early adopters!
https://github.com/elixir-tools/next-ls
elixir lsp
Last synced: 5 months ago
JSON representation
The language server for Elixir that just works. Ready for early adopters!
- Host: GitHub
- URL: https://github.com/elixir-tools/next-ls
- Owner: elixir-tools
- License: mit
- Created: 2022-07-16T05:21:50.000Z (about 3 years ago)
- Default Branch: main
- Last Pushed: 2025-04-08T13:03:46.000Z (6 months ago)
- Last Synced: 2025-04-14T01:05:09.420Z (6 months ago)
- Topics: elixir, lsp
- Language: Elixir
- Homepage: https://www.elixir-tools.dev/next-ls
- Size: 21 MB
- Stars: 734
- Watchers: 7
- Forks: 39
- Open Issues: 68
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
Awesome Lists containing this project
README
> [!IMPORTANT]
> Next LS is merging with Elixir LS and Lexical! Read more about it at [www.elixir-tools.dev.](https://www.elixir-tools.dev/news/the-elixir-tools-update-vol-7/)
# Next LS
[](https://www.elixir-tools.dev/docs/next-ls/quickstart)
[](https://github.com/elixir-tools/next-ls/releases)
[)](https://github.com/elixir-tools/next-ls/releases)
[](https://github.com/orgs/elixir-tools/discussions)
[](https://discord.gg/6XdGnxVA2A)
The language server for Elixir that just works. 😎
Still in heavy development, but early adopters are encouraged!
Please see the [docs](https://www.elixir-tools.dev/docs/next-ls/quickstart) to get started.
## Related Links
- [Introducing Next LS and an elixir-tools update](https://www.elixir-tools.dev/news/introducing-next-ls-and-an-elixir-tools-update/)
- [The elixir-tools Update Vol. 2](https://www.elixir-tools.dev/news/the-elixir-tools-update-vol-2/)
- [The elixir-tools Update Vol. 3](https://www.elixir-tools.dev/news/the-elixir-tools-update-vol-3/)
- [The elixir-tools Update Vol. 4](https://www.elixir-tools.dev/news/the-elixir-tools-update-vol-4/)
- [The 2023 elixir-tools Update (Vol. 5) ](https://www.elixir-tools.dev/news/the-2023-elixir-tools-update-vol-5/)
- [The elixir-tools Update Vol. 6](https://www.elixir-tools.dev/news/the-elixir-tools-update-vol-6/)
- [The elixir-tools Update Vol. 7 & The Great Merge](https://www.elixir-tools.dev/news/the-elixir-tools-update-vol-7/)
## 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
### Remaining tiers
## Development
Next LS uses [just](https://github.com/casey/just) to coordinate command tasks.
```bash
# list all tasks
just --list
# show a fzf finder of all tasks
just choose
# default task, runs `deps compile build-local
just
# install deps
just deps
# install compile
just compile
# 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
just start
# run the tests
just test
# build a local burrito'd exe
just build-local
# build burrito'd exes for all platforms
just build-all
```
## Production release
### Burrito
Burrito is the classic way of building Next LS, it produces a single executable that fully wraps Elixir, OTP, and your application.
Executables are output to `./burrito_out`.
```bash
# produces executables for all the targets specified in the `mix.exs` file
just build-all
# produce an executable for a single target
just build-local
```
### Traditional
You can also build Next LS as a traditional Mix release.
```bash
just build-plain
```
## Contributing
This project follows [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) 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](https://github.com/googleapis/release-please), which is used to automate the changelog, release, and building/publishing executables.