---
title: "Discussion on \"Neovim, Deno, and TypeScript in a monorepo\" | Hashnode"
description: "Discussion on \"Neovim, Deno, and TypeScript in a monorepo\". How to avoid LSP conflicts"
url: "https://hashnode.com/posts/neovim-deno-and-typescript-in-a-monorepo/654d8b07aba259749fa2232d"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Neovim, Deno, and TypeScript in a monorepo](https://npbee.hashnode.dev/neovim-deno-and-typescript-in-a-monorepo?utm_source=hashnode&utm_medium=feed)

How to avoid LSP conflicts

Nov 10, 2023 · 2 min read · npbee.hashnode.dev  
Read the article

-   [#deno](https://hashnode.com/tag/deno)
-   [#neovim](https://hashnode.com/tag/neovim)
-   [#monorepo](https://hashnode.com/tag/monorepo)
-   [#typescript](https://hashnode.com/tag/typescript)
-   [#lsp](https://hashnode.com/tag/lsp)

## Written by

[Nick Ball](https://hashnode.com/@npbee)

@npbee · Portland, OR

  
[View profile](https://hashnode.com/@npbee)

Software developer + dad based in Portland, Oregon. Past: Musician. Currently at Dropbox.

I'm a software engineer based in Portland, Oregon. I specialize in frontend development and enjoy component-based architecture, typography, and getting the details just right. I write a lot of TypeScript and React with a dash of Svelte and Astro on the side. I love building delightful, practical, and accessible user experiences that help people get things done. I currently work as a software engineer at Dropbox building the Forms application.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.