Home Web Front-end JS Tutorial How to setup VueJs in Neovim (January 5)

How to setup VueJs in Neovim (January 5)

Jan 03, 2025 pm 07:58 PM

Hello, I had issues setting up neovim with vuejs plugins, so I am sharing the knowledge on how I got it to work.

This article assumes basic knowledge on how to add and modify your plugins with LazyVim.

I am using kickstart.nvim.

Packages that we will use : blink.cmp for autocompletion, typescript-tools for the typescript LSP, neovim/nvim-lspconfig to set up the LSP, and Mason so we can install volar.

1) Typescript-tools setup:

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

return {

  'pmizio/typescript-tools.nvim',

  dependencies = { 'nvim-lua/plenary.nvim', 'neovim/nvim-lspconfig' },

  opts = {},

  ft = { 'javascript', 'javascriptreact', 'typescript', 'typescriptreact', 'vue' },

  config = function()

    require('typescript-tools').setup {

      on_attach = function(client, bufnr)

        client.server_capabilities.documentFormattingProvider = false

        client.server_capabilities.documentRangeFormattingProvider = false

      end,

      filetypes = {

        'javascript',

        'javascriptreact',

        'typescript',

        'typescriptreact',

        'vue',

      },

      settings = {

        tsserver_plugins = {

          '@vue/typescript-plugin',

        },

        jsx_close_tag = {

          enable = true,

          filetypes = { 'javascriptreact', 'typescriptreact' },

        },

      },

    }

  end,

}

Copy after login

This is typescript-tools. It is tsserver, but faster.

In the tsserver_plugins table, we are calling @vue/typescript-plugin.

The recent versions of Volar, it embeds itself in the typescript LSP, providing it with capabilities.

We have to actually install this plugin.
Ideally on a per project basis, I installed it globally as of right now.
npm i -g @vue/typescript-plugin

2) LspConfig:
We are using neovim/nvim-lspconfig to set up the lsp functionalities.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

61

62

63

64

65

66

67

68

69

70

71

72

73

74

75

76

77

78

79

80

return {

    'neovim/nvim-lspconfig',

    dependencies = {

      { 'williamboman/mason.nvim', config = true },

      'williamboman/mason-lspconfig.nvim',

      'WhoIsSethDaniel/mason-tool-installer.nvim',

      { 'j-hui/fidget.nvim', opts = {} },

      'saghen/blink.cmp',

    },

    config = function()

      local capabilities = vim.lsp.protocol.make_client_capabilities()

      capabilities = require('blink.cmp').get_lsp_capabilities(capabilities)

 

      local servers = {

        volar = { 'vue' },

        lua_ls = {

          settings = {

            Lua = {

              completion = { callSnippet = 'Replace' },

            },

          },

        },

      }

 

      require('mason').setup()

 

      local ensure_installed = vim.tbl_keys(servers)

      -- vim.list_extend(ensure_installed, { 'stylua' })

      require('mason-tool-installer').setup { ensure_installed = ensure_installed }

 

      -- Setup mason-lspconfig

      require('mason-lspconfig').setup {

        ensure_installed = ensure_installed,

        handlers = {

          function(server_name)

            local opts = servers[server_name] or {}

            opts.capabilities = vim.tbl_deep_extend('force', {}, capabilities, opts.capabilities or {})

            require('lspconfig')[server_name].setup(opts)

          end,

        },

      }

 

      -- Setup LspAttach autocmd for keymaps and additional functionality

      vim.api.nvim_create_autocmd('LspAttach', {

        group = vim.api.nvim_create_augroup('kickstart-lsp-attach', { clear = true }),

        callback = function(event)

          local map = function(keys, func, desc, mode)

            mode = mode or 'n'

            vim.keymap.set(mode, keys, func, { buffer = event.buf, desc = 'LSP: ' .. desc })

          end

 

          map('gd', require('telescope.builtin').lsp_definitions, '[G]oto [D]efinition')

          map('gr', require('telescope.builtin').lsp_references, '[G]oto [R]eferences')

          map('gI', require('telescope.builtin').lsp_implementations, '[G]oto [I]mplementation')

          map('<leader>D', require('telescope.builtin').lsp_type_definitions, 'Type [D]efinition')

          map('<leader>ds', require('telescope.builtin').lsp_document_symbols, '[D]ocument [S]ymbols')

          map('<leader>ws', require('telescope.builtin').lsp_dynamic_workspace_symbols, '[W]orkspace [S]ymbols')

          map('<leader>cr', vim.lsp.buf.rename, '[R]e[n]ame')

          map('<leader>ca', vim.lsp.buf.code_action, '[C]ode [A]ction', { 'n', 'x' })

          map('gD', vim.lsp.buf.declaration, '[G]oto [D]eclaration')

 

          local client = vim.lsp.get_client_by_id(event.data.client_id)

          if client and client.supports_method(vim.lsp.protocol.Methods.textDocument_documentHighlight) then

            local highlight_group = vim.api.nvim_create_augroup('kickstart-lsp-highlight', { clear = false })

            vim.api.nvim_create_autocmd({ 'CursorHold', 'CursorHoldI' },

{

              buffer = event.buf,

              group = highlight_group,

              callback = vim.lsp.buf.document_highlight,

            })

            vim.api.nvim_create_autocmd({ 'CursorMoved', 'CursorMovedI'}, {

              buffer = event.buf,

              group = highlight_group,

              callback = vim.lsp.buf.clear_references,

            })

          end

        end,

      })

    end,

  },

Copy after login

The most important thing here is that we are passing blink.cmp and that we are setting up volar as our LSP for .vue files.

Open up neovim and install volar.

1

:MasonInstall vue-language-server

Copy after login

Restart Neovim and this should be it. You should have all the functionalities, go to definition, go to reference, lsp errors etc.

How to setup VueJs in Neovim (January 5)

Autocomplete config

If you have a functional autocomplete plugin, ignore this.
I am going to share my config for blink.cmp in case you need one.

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

61

62

63

64

65

66

67

68

69

70

71

72

73

74

75

76

77

78

79

80

81

82

83

84

85

86

87

88

89

90

91

92

93

94

95

96

97

98

99

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

return {

    'saghen/blink.cmp',

    -- dependencies = { 'rafamadriz/friendly-snippets', 'onsails/lspkind.nvim' },

    dependencies = { 'onsails/lspkind.nvim' },

 

    version = '*',

    ---@module 'blink.cmp'

    ---

    ---@type blink.cmp.Config

 

    opts = {

      keymap = {

        ['<C-space>'] = { 'show', 'show_documentation', 'hide_documentation' },

        ['<C-e>'] = { 'hide', 'fallback' },

        ['<CR>'] = { 'accept', 'fallback' },

 

        ['<Tab>'] = {

          function(cmp)

            return cmp.select_next()

          end,

          'snippet_forward',

          'fallback',

        },

        ['<S-Tab>'] = {

          function(cmp)

            return cmp.select_prev()

          end,

          'snippet_backward',

          'fallback',

        },

 

        ['<Up>'] = { 'select_prev', 'fallback' },

        ['<Down>'] = { 'select_next', 'fallback' },

        ['<C-p>'] = { 'select_prev', 'fallback' },

        ['<C-n>'] = { 'select_next', 'fallback' },

        ['<C-up>'] = { 'scroll_documentation_up', 'fallback' },

        ['<C-down>'] = { 'scroll_documentation_down', 'fallback' },

      },

 

      appearance = {

        use_nvim_cmp_as_default = true,

        nerd_font_variant = 'mono',

      },

 

      completion = {

        accept = {

          auto_brackets = {

            enabled = true,

          },

        },

 

        list = {

          selection = function(ctx)

            return ctx.mode == 'cmdline' and 'auto_insert' or 'preselect'

          end,

        },

        --

        menu = {

          border = 'rounded',

 

          cmdline_position = function()

            if vim.g.ui_cmdline_pos ~= nil then

              local pos = vim.g.ui_cmdline_pos -- (1, 0)-indexed

              return { pos[1] - 1, pos[2] }

            end

            local height = (vim.o.cmdheight == 0) and 1 or vim.o.cmdheight

            return { vim.o.lines - height, 0 }

          end,

 

          draw = {

            columns = {

              { 'kind_icon', 'label', gap = 1 },

              { 'kind' },

            },

            components = {

              kind_icon = {

                text = function(item)

                  local kind = require('lspkind').symbol_map[item.kind] or ''

                  return kind .. ' '

                end,

                highlight = 'CmpItemKind',

              },

              label = {

                text = function(item)

                  return item.label

                end,

                highlight = 'CmpItemAbbr',

              },

              kind = {

                text = function(item)

                  return item.kind

                end,

                highlight = 'CmpItemKind',

              },

            },

          },

        },

      },

      sources = {

        default = { 'lsp', 'path', 'buffer', 'snippets' },

        cmdline = {},

        providers = {

          lsp = {

            min_keyword_length = 2, -- Number of characters to trigger porvider

            score_offset = 0, -- Boost/penalize the score of the items

          },

          path = {

            min_keyword_length = 0,

          },

          snippets = {

            min_keyword_length = 2,

          },

          buffer = {

            min_keyword_length = 2,

          },

        },

      },

    },

  },

Copy after login

The above is the detailed content of How to setup VueJs in Neovim (January 5). For more information, please follow other related articles on the PHP Chinese website!

Statement of this Website
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn

Hot AI Tools

Undresser.AI Undress

Undresser.AI Undress

AI-powered app for creating realistic nude photos

AI Clothes Remover

AI Clothes Remover

Online AI tool for removing clothes from photos.

Undress AI Tool

Undress AI Tool

Undress images for free

Clothoff.io

Clothoff.io

AI clothes remover

Video Face Swap

Video Face Swap

Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Roblox: Bubble Gum Simulator Infinity - How To Get And Use Royal Keys
3 weeks ago By 尊渡假赌尊渡假赌尊渡假赌
Nordhold: Fusion System, Explained
3 weeks ago By 尊渡假赌尊渡假赌尊渡假赌
Mandragora: Whispers Of The Witch Tree - How To Unlock The Grappling Hook
3 weeks ago By 尊渡假赌尊渡假赌尊渡假赌

Hot Tools

Notepad++7.3.1

Notepad++7.3.1

Easy-to-use and free code editor

SublimeText3 Chinese version

SublimeText3 Chinese version

Chinese version, very easy to use

Zend Studio 13.0.1

Zend Studio 13.0.1

Powerful PHP integrated development environment

Dreamweaver CS6

Dreamweaver CS6

Visual web development tools

SublimeText3 Mac version

SublimeText3 Mac version

God-level code editing software (SublimeText3)

Hot Topics

Java Tutorial
1664
14
PHP Tutorial
1269
29
C# Tutorial
1249
24
JavaScript Engines: Comparing Implementations JavaScript Engines: Comparing Implementations Apr 13, 2025 am 12:05 AM

Different JavaScript engines have different effects when parsing and executing JavaScript code, because the implementation principles and optimization strategies of each engine differ. 1. Lexical analysis: convert source code into lexical unit. 2. Grammar analysis: Generate an abstract syntax tree. 3. Optimization and compilation: Generate machine code through the JIT compiler. 4. Execute: Run the machine code. V8 engine optimizes through instant compilation and hidden class, SpiderMonkey uses a type inference system, resulting in different performance performance on the same code.

Python vs. JavaScript: The Learning Curve and Ease of Use Python vs. JavaScript: The Learning Curve and Ease of Use Apr 16, 2025 am 12:12 AM

Python is more suitable for beginners, with a smooth learning curve and concise syntax; JavaScript is suitable for front-end development, with a steep learning curve and flexible syntax. 1. Python syntax is intuitive and suitable for data science and back-end development. 2. JavaScript is flexible and widely used in front-end and server-side programming.

From C/C   to JavaScript: How It All Works From C/C to JavaScript: How It All Works Apr 14, 2025 am 12:05 AM

The shift from C/C to JavaScript requires adapting to dynamic typing, garbage collection and asynchronous programming. 1) C/C is a statically typed language that requires manual memory management, while JavaScript is dynamically typed and garbage collection is automatically processed. 2) C/C needs to be compiled into machine code, while JavaScript is an interpreted language. 3) JavaScript introduces concepts such as closures, prototype chains and Promise, which enhances flexibility and asynchronous programming capabilities.

JavaScript and the Web: Core Functionality and Use Cases JavaScript and the Web: Core Functionality and Use Cases Apr 18, 2025 am 12:19 AM

The main uses of JavaScript in web development include client interaction, form verification and asynchronous communication. 1) Dynamic content update and user interaction through DOM operations; 2) Client verification is carried out before the user submits data to improve the user experience; 3) Refreshless communication with the server is achieved through AJAX technology.

JavaScript in Action: Real-World Examples and Projects JavaScript in Action: Real-World Examples and Projects Apr 19, 2025 am 12:13 AM

JavaScript's application in the real world includes front-end and back-end development. 1) Display front-end applications by building a TODO list application, involving DOM operations and event processing. 2) Build RESTfulAPI through Node.js and Express to demonstrate back-end applications.

Understanding the JavaScript Engine: Implementation Details Understanding the JavaScript Engine: Implementation Details Apr 17, 2025 am 12:05 AM

Understanding how JavaScript engine works internally is important to developers because it helps write more efficient code and understand performance bottlenecks and optimization strategies. 1) The engine's workflow includes three stages: parsing, compiling and execution; 2) During the execution process, the engine will perform dynamic optimization, such as inline cache and hidden classes; 3) Best practices include avoiding global variables, optimizing loops, using const and lets, and avoiding excessive use of closures.

Python vs. JavaScript: Community, Libraries, and Resources Python vs. JavaScript: Community, Libraries, and Resources Apr 15, 2025 am 12:16 AM

Python and JavaScript have their own advantages and disadvantages in terms of community, libraries and resources. 1) The Python community is friendly and suitable for beginners, but the front-end development resources are not as rich as JavaScript. 2) Python is powerful in data science and machine learning libraries, while JavaScript is better in front-end development libraries and frameworks. 3) Both have rich learning resources, but Python is suitable for starting with official documents, while JavaScript is better with MDNWebDocs. The choice should be based on project needs and personal interests.

Python vs. JavaScript: Development Environments and Tools Python vs. JavaScript: Development Environments and Tools Apr 26, 2025 am 12:09 AM

Both Python and JavaScript's choices in development environments are important. 1) Python's development environment includes PyCharm, JupyterNotebook and Anaconda, which are suitable for data science and rapid prototyping. 2) The development environment of JavaScript includes Node.js, VSCode and Webpack, which are suitable for front-end and back-end development. Choosing the right tools according to project needs can improve development efficiency and project success rate.

See all articles