Erik Kinnunen

Thanks @chrissimon-au for clarification! In our environment, we have a diverse group of individuals using various IDEs, including both those we are familiar with and those we may not be...

The approach of utilizing a separate configuration file aligns with the [Project Local Config](https://github.com/neovim/nvim-lspconfig/wiki/Project-local-settings#use-native-server-file-configs) solution. This method is generally more developer-friendly, as the alternative options introduce additional tooling or personal...

> Hi @erikjuhani , ok, I can see the rationale now. That `Project Local Config` page seems to offer 4 options, one of which is [Use native server file configs](https://github.com/neovim/nvim-lspconfig/wiki/Project-local-settings#use-native-server-file-configs),...

I solved this in a hacky way by invoking default: ```ts // @ts-expect-error https://github.com/originjs/vite-plugins/issues/54 ViteRequireContext.default(), ```

> Hey, really sorry I left this hanging for so long. We were busy doing the big express release and then I needed to take a bit of time to...

> Also I realised that there's a slight mishap in this PR. I think the new dependencies should be defined under `dependencies` and not under `devDependencies` as these are consumer...

Tests are breaking, but it's unrelated to my package.json change and I believe it's caused by the new minor version releases in express.