What are good general guidelines/tips for someone writing a plugin in Lua?

This page summarizes the projects mentioned and recommended in the original post on /r/neovim

Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
  • plugin-template.nvim

    A template to create Neovim plugins written in Lua

  • Hello everyone, I created a plugin template for Neovim before and now I'm planning to add a general guidelines section to its documentation. To not make this too personal I'd like to hear from you what are good tips, guidelines, do/don't, etc. when writing a Lua plugin. Does anyone here have strong opinions on this?

  • package-info.nvim

    ✍️ All the npm/yarn/pnpm commands I don't want to type

  • Keep the code splitting simple. When i was writing initial version of package-info I split stuff into multiple files, tried to make it all "nice" and organized. What that did is just complicated things and when and

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

    InfluxDB logo
  • baleia.nvim

    Colorize text with ANSI escape sequences (8, 16, 256 or TrueColor)

  • I have mixed feeling about this one. With proper editor setup for Lua I find easy to navigate though the code and smaller files make testing feel simpler... at leas that was my impression while writing https://github.com/m00qek/baleia.nvim

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts