module 'lsp_signature' not found

[WilliamLeslieHarrison]

on startup i recieve the error:

        no field package.preload['lsp_signature']
        no file '/home/william/.local/share/lua/lsp_signature.lua'
        no file '/home/william/.local/share/lua/lsp_signature/init.lua'
        no file './lsp_signature.lua'
        no file '/usr/share/luajit-2.1.0-beta3/lsp_signature.lua'
        no file '/usr/local/share/lua/5.1/lsp_signature.lua'
        no file '/usr/local/share/lua/5.1/lsp_signature/init.lua'
        no file '/usr/share/lua/5.1/lsp_signature.lua'
        no file '/usr/share/lua/5.1/lsp_signature/init.lua'
        no file '/home/william/.cache/nvim/packer_hererocks/2.1.0-beta3/share/lua/5.1/lsp_signature.lua'
        no file '/home/william/.cache/nvim/packer_hererocks/2.1.0-beta3/share/lua/5.1/lsp_signature/init.lua'
        no file '/home/william/.cache/nvim/packer_hererocks/2.1.0-beta3/lib/luarocks/rocks-5.1/lsp_signature.lua'
        no file '/home/william/.cache/nvim/packer_hererocks/2.1.0-beta3/lib/luarocks/rocks-5.1/lsp_signature/init.lua'
        no file './lsp_signature.so'
        no file '/usr/local/lib/lua/5.1/lsp_signature.so'
        no file '/usr/lib/lua/5.1/lsp_signature.so'
        no file '/usr/local/lib/lua/5.1/loadall.so'
        no file '/home/william/.cache/nvim/packer_hererocks/2.1.0-beta3/lib/lua/5.1/lsp_signature.so'
stack traceback:
        [C]: in function 'require'
        /home/william/.config/nvim/lua/plugins/lsp/lsp.lua:7: in function '_on_attach'
        ...pack/packer/opt/nvim-lspconfig/lua/lspconfig/configs.lua:280: in function '_setup_buffer'
        ...pack/packer/opt/nvim-lspconfig/lua/lspconfig/configs.lua:183: in function 'cb'
        vim/_editor.lua:256: in function <vim/_editor.lua:256>

i tried running PackerSync and restarting neovim, but the error persists, however removing the event key in lsp_signatures use statement in plugins.lua and rerunning PackerSync fixes the issue, if this is change you would accept, i can make a PR

[aaryswastaken]

I also have that issue, is there another way to handle this?