Migrate to monorepo

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,10 +1,9 @@
 ---
 name: Bug report
 about: Create a report to help us improve
-title: ''
+title: ""
 labels: bug
-assignees: ''
-
+assignees: ""
 ---
 
 **Describe the bug**

.gitignore

@@ -3,3 +3,6 @@ dist
 node_modules
 .vscode-test/
 *.vsix
+.turbo
+.vercel
+**/.DS_Store

.prettierrc

@@ -0,0 +1,6 @@
+{
+  "printWidth": 80,
+  "tabWidth": 2,
+  "useTabs": false,
+  "trailingComma": "es5"
+}

README.md

@@ -8,52 +8,56 @@
 
 # Pretty `TypeScript` Errors
 
-<b>Make TypeScript errors prettier and human-readable in VSCode.</b>  
-  
+<b>Make TypeScript errors prettier and human-readable in VSCode.</b>
+
 [![Visual Studio Code](https://img.shields.io/badge/--007ACC?logo=visual%20studio%20code&logoColor=ffffff)](https://marketplace.visualstudio.com/items?itemName=yoavbls.pretty-ts-errors)&nbsp;[![GitHub license](https://badgen.net/github/license/yoavbls/pretty-ts-errors)](https://github.com/yoavbls/pretty-ts-errors/blob/main/LICENSE)&nbsp;![visitor badge](https://visitor-badge.glitch.me/badge?page_id=pretty-ts-errors)
 [![GitHub stars](https://img.shields.io/github/stars/yoavbls/pretty-ts-errors.svg?style=social&label=Star)](https://GitHub.com/yoavbls/pretty-ts-errors/stargazers/)
 
-<a href="https://github.com/yoavbls/pretty-ts-errors/discussions/43"><img src="https://raw.githubusercontent.com/yoavbls/pretty-ts-errors/assets/assets/mentions/vote.png" width="490px" /></a>  
+<a href="https://github.com/yoavbls/pretty-ts-errors/discussions/43"><img src="https://raw.githubusercontent.com/yoavbls/pretty-ts-errors/assets/assets/mentions/vote.png" width="490px" /></a>
 
 TypeScript errors become messier as the complexity of types increases. At some point, TypeScript will throw on you a shitty heap of parentheses and `"..."`.  
 This extension will help you understand what's going on. For example, in this relatively simple error:
 
-<img src="./assets/this.png" width="340.438px" />&nbsp; &nbsp; <img src="./assets/instead-of-that.png" width="350px" />  
-
-
+<img src="./assets/this.png" width="340.438px" />&nbsp; &nbsp; <img src="./assets/instead-of-that.png" width="350px" />
+
 ## Watch this
+
 <a href="https://www.youtube.com/watch?v=9RM2aErJs-s" target="_blank">
  <img src="https://raw.githubusercontent.com/yoavbls/pretty-ts-errors/assets/assets/mentions/theo-video.png" alt="Watch theo's video" width="600" />
 </a>
 
 ## Features
+
 - Syntax highlighting with your theme colors for types in error messages, supporting both light and dark themes
 - A button that leads you to the relevant type declaration next to the type in the error message
 - A button that navigates you to the error at [typescript.tv](http://typescript.tv), where you can find a detailed explanation, sometimes with a video
 - A button that navigates you to [ts-error-translator](https://ts-error-translator.vercel.app/), where you can read the error in plain English
 
 ## Supports
+
 - Node and Deno TypeScript error reporters (in `.ts` files)
 - JSDoc type errors (in `.js` and `.jsx` files)
 - React, Solid and Qwik errors (in `.tsx` and `.mdx` files)
 - Astro, Svelte and Vue files when TypeScript is enabled (in `.astro`, `.svelte` and `.vue` files)
-
-
+
 ## Installation
+
 ```
 code --install-extension yoavbls.pretty-ts-errors
 ```
-Or simply by searching for `pretty-ts-errors` in the [VSCode marketplace](https://marketplace.visualstudio.com/items?itemName=yoavbls.pretty-ts-errors)  
-  
-  
+
+Or simply by searching for `pretty-ts-errors` in the [VSCode marketplace](https://marketplace.visualstudio.com/items?itemName=yoavbls.pretty-ts-errors)
+
 ## Why isn't it trivial
+
 1. TypeScript errors contain types that are not valid in TypeScript.  
-Yes, these types include things like `... more ...`, `{ ... }`, etc in an inconsistent manner. Some are also cutting in the middle because they're too long.
+   Yes, these types include things like `... more ...`, `{ ... }`, etc in an inconsistent manner. Some are also cutting in the middle because they're too long.
 2. Types can't be syntax highlighted in code blocks because the part of `type X = ...` is missing, so I needed to create a new TextMate grammar, a superset of TypeScript grammar called `type`.
 3. VSCode markdown blocks all styling options, so I had to find hacks to style the error messages. e.g., there isn't an inlined code block on VSCode markdown, so I used a code block inside a codicon icon, which is the only thing that can be inlined. That's why it can't be copied. but it isn't a problem because you can still hover on the error and copy things from the original error pane.  
-<img src="./assets/errors-hover.png" width="600" /> 
+   <img src="./assets/errors-hover.png" width="600" />
 
 ## Hype section
+
 <a href="https://twitter.com/t3dotgg/status/1647759462709747713">
   <picture>    
     <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/yoavbls/pretty-ts-errors/assets/assets/mentions/theo-dark.png#gh-dark-mode-only">
@@ -76,8 +80,8 @@ Yes, these types include things like `... more ...`, `{ ... }`, etc in an incons
   </picture>
 </a>
 
-  
-### Stars from stars  
+### Stars from stars
+
 <table>
   <tbody>
     <tr>
@@ -115,14 +119,12 @@ Yes, these types include things like `... more ...`, `{ ... }`, etc in an incons
   </tbody>
 </table>
 
-
 ## Sponsorship
+
 Every penny will be invested in other contributors to the project, especially ones that work  
 on things that I can't be doing myself like adding support to the extension for other IDEs 🫂
-  
+
 ## Contribution
+
 Help by upvoting or commenting on issues we need to be resolved [here](https://github.com/yoavbls/pretty-ts-errors/discussions/43)  
 Any other contribution is welcome. Feel free to open any issue / PR you think.
-
-
-