vscode-eslint
VSCode extension to integrate eslint into VSCode (by microsoft)
packspec
ALPHA package dependencies spec (by neovim)
SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
surveyjs.io
featured
vscode-eslint | packspec | |
---|---|---|
3 | 7 | |
1,687 | 205 | |
1.8% | 2.0% | |
7.7 | 4.8 | |
4 days ago | 3 months ago | |
TypeScript | Lua | |
MIT License | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
vscode-eslint
Posts with mentions or reviews of vscode-eslint.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-04-17.
-
Breaking changes inbound (next few weeks) for lspconfig and neovim's language server client lsp
vscode-eslint does implement an LSP bridge which is lspconfig provides.
-
TypeScript: ESLint code actions and (experimental) diagnostics / formatting
I've recently added support for ESLint code actions to my plugin nvim-lsp-ts-utils, a feature some users expressed interest in the last time I posted about the plugin here. The implementation supports most of the features from vscode-eslint, including applying fixes and disabling rules for the current line / file:
-
Format Glimmer templates with Prettier
Please refer to official documentation for ESLint extension for VSCode for details.
packspec
Posts with mentions or reviews of packspec.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-02-10.
- This Week In Neovim #31 – Mon Feb 13 2023
-
Introducing Luarocks-Tag-Release - Publish your Neovim plugins to LuaRocks
It looks like there's a WIP package specification that might also support source = luarocks://.
-
Standardizing Neovim package management API - could or should this be a thing? Let’s talk about it!
I was hoping you would clarify exactly what you're proposing so I could forward the appropriate link, otherwise I'm just guess based off a vague (but long) post. Based on other replies in this reddit post, I'm not the only one confused by your ambiguous and likely incorrect terminology. It sounds like you're looking for a specification, which exists https://github.com/nvim-lua/nvim-package-specification, it just isn't well adopted. There's also countless Github issues and discussions about this on IRC which you could find by a simple Google search. It really just depends on what you're alluding to which is why I linked what an API was so you could be more specific. If you're looking for the plugin managers API (notice the qualifier) to be consistent, then that's not a good idea since the API of the plugin manager is what differentiates them, it's like saying all programming languages should be the same, the only thing different should be the backend (e.g. gcc vs llvm). The consistency should be at a different layer (thus the plugin spec).
-
Breaking changes inbound (next few weeks) for lspconfig and neovim's language server client lsp
packspec, a package specification for neovim to address the dependency issue
-
Opinion on better plugin management?
There is an issue for it: https://github.com/nvim-lua/nvim-package-specification/issues/23
What are some alternatives?
When comparing vscode-eslint and packspec you can also consider the following projects:
nvim-lsp-ts-utils - Utilities to improve the TypeScript development experience for Neovim's built-in LSP client.
lazy.nvim - 💤 A modern plugin manager for Neovim
ember-template-lint - Linter for Ember or Handlebars templates
nvim-conf - ☄ Maddison's Neovim configuration!
efm-langserver - General purpose Language Server
luarocks - LuaRocks is the package manager for the Lua programming language.
lsp-format.nvim - A wrapper around Neovims native LSP formatting.
diagnostic-languageserver - diagnostic language server integrate with linters
neovim - Vim-fork focused on extensibility and usability
prettier - Prettier is an opinionated code formatter.
fabn
vscode-eslint vs nvim-lsp-ts-utils
packspec vs lazy.nvim
vscode-eslint vs ember-template-lint
packspec vs nvim-conf
vscode-eslint vs efm-langserver
packspec vs luarocks
vscode-eslint vs lsp-format.nvim
packspec vs lsp-format.nvim
vscode-eslint vs diagnostic-languageserver
packspec vs neovim
vscode-eslint vs prettier
packspec vs fabn