I'm not sure why you need the if true then clause at the beginning of your spec. Just return the spec without it.

Thx for your respone!

I'm not sure why you need the if true then clause at the beginning of your spec. Just return the spec without it.

I added the if true then because I said

change the ${HOME}/.config/${NVIM_APPNAME}/lua/plugins/example.lua so it starts with [...]

If you don't prepend the file with that code, but replace the whole content, you can lose the if true then. However, this does not change the outcome.

1. git clone https://github.com/LazyVim/starter ~/.config/lazyTest
2. NVIM_APPNAME=lazyTest nvim
3. Nvim installs all necessary plugins
4. Create file test.lua in ~/.config/lazyTest/lua/plugins/ directory with following contents

return {
  {
    "nvim-treesitter/nvim-treesitter",
    opts = function(_, opts)
      -- add tsx and treesitter
      vim.list_extend(opts.ensure_installed, {
        "tsx",
        "typescript",
      })
    end,
  },
}

5. Close Neovim and open again with NVIM_APPNAME=lazyTest nvim. tsx and typescript get installed as can be seen in :TSInstallInfo with no errors whatsoever.
   I don't know what you did wrong but I don't get any errors with this procedure which is simulating the steps you took.

To ensure it's not somehow my system I re-created the issue in a docker:

1. Create a Dockerfile with the content

FROM ubuntu:22.04

RUN apt-get update \
  && apt-get install -y \
    curl \
    git \
    ninja-build \
    g++ \
    gettext \
    cmake \
    unzip \
    curl

# https://github.com/neovim/neovim/wiki/Installing-Neovim#appimage-universal-linux-package
RUN curl -LO https://github.com/neovim/neovim/releases/latest/download/nvim.appimage \
  && chmod u+x nvim.appimage \
  && ./nvim.appimage --appimage-extract \
  && ln -s /squashfs-root/AppRun /usr/bin/nvim

RUN mkdir -p /root/.config \
  && git clone https://github.com/LazyVim/starter /root/.config/nvim

COPY test.lua /root/.config/nvim/lua/plugins/

2. next to the Dockerfile create a test.lua with the content

return {
  {
    "nvim-treesitter/nvim-treesitter",
    opts = function(_, opts)
      -- add tsx and treesitter
      vim.list_extend(opts.ensure_installed, {
        "tsx",
        "typescript",
      })
    end,
  },
}

3. run the following

docker build -t lazyvim-issue . && docker run --rm -it lazyvim-issue

4. in that container start nvim. this should install all plugins, with a minor issue (LuaSnip - let's ignore that one)
5. close nvim using :q
6. restart nvim with nvim /root/.bashrc

You should see a lot of errors.

Aside from the container, I'm able to produce it on two different linux systems (Ubuntu 20.04 and OpenSuse tumbleweed) on different hardware.

Can you can confirm it now? 😱

here is a screen capture of the issue https://calip.io/MxW6AeUZ#CYYVeBS4

I added g++ to the Dockerfile to get a cleaner issue

No i can't confirm it. As i did it there were no errors. I use neovim latest nightly build and i don't know what version the latest appimage is. Maybe an issue with Neovim version? I don't know what to tell you since i did not encounter the errors you're talking about.

Should be fixed now. I didn't have this issue since I just override the whole list

@folke Just out of curiosity I don't override the whole list myself, rather I vim.list_extend to ensure_installed table whatever I want. Why did this not happen to me? In my second post I also created a new instance of Neovim from the starter template seperate from the one I already have using the new NVIM_APPNAME variable to distinguish between the 2 and just extended the treesitter options again and did not encounter the problem either.

No idea. I also didn't have this problem when testing regular LazyVim.
I think the problem doesn't always happen and should honestly also just be fixed in nvim-treesitter if that can indeed cause issues.

Tested. Works well. Thx for the fast responses and fix! 😍

I think the problem doesn't always happen and should honestly also just be fixed in nvim-treesitter if that can indeed cause issues.

I hear you. I tried to forward the issue