🧩 Plasmo Developers

Question about auto generated tsconfig.json

This isn't entirely related to Plasmo, maybe. Regardless, I want to check out if this is a common thing or if it's just my setup.

Are Plasmo types and imports properly configured? VS Code doesn't seem to recognize them, at least for auto importing and what not.

<@973659943469215754> has reached level **1**. GG!

This sometimes happens with VS Code, if it's the same issue I'm thinking about

Can you try:
```
command-shift-p
reload window
```

Sorry for not replying earlier, but that didn't work. I've already tried quite a few things, even reinstalling VS Code from scratch without any plugins to no avail. At least I'm glad to know that it's something related to my local setup

Hey, so after some testing this is quite bizarre

It works fine with the already existing example (`with-content-scripts-ui`), but a project made from scratch won't work, even when they are practically the same

The only differences between both projects are the contents of the `contents` folder (which shouldn't really matter), and that's it

the `tsconfig` and `package.json` are the same in both, so I'm quite surprised

Try this steps to reproduce

1. Install the dependencies on the `with-content-scripts-ui` example.
2. Try to write something that should be automatically imported and detected by IntelliSense. It should work.
3. Remove all of the files inside the `contents` folder, except `plasmo-overlay.tsx`
4. Try the same as step 2, it shouldn't work anymore

```
import type { PlasmoContentScript } from "plasmo"
```

You must have that import statement ^ 

VS Code auto-adds it for you in the first example because it exists in other files in the directory. But for your example, it doesn't exist anywhere else

We'll see how we can better hint to VS Code that `PlasmoContentScript` can be imported from the `plasmo` package 

<@353228093420208131> for visibility ^^

Updated auto-threading settings for <#983821094056243270>