![]() ![]() I am using VSCode version 1.78.2 on a MacBook M2 v13.4 with Node v18.16.0 if that helps, with TypeScript. How else can I fix this, so when I either pnpm link symlink a local module, or install a new version of a module, that it picks up the changes without a full VSCode restart? ![]() My only solution so far is to quit VSCode and reopen it. But instead, VSCode doesn't seem to pick up the change, and it shows errors for what I am trying to access in the foo library (If I change/add/remove something from foo let's say). When I close the file which imported foo and open it up again, usually I would expect VSCode to pick up the change and note the new version of the library (that is my experience with npm and yarn in the past). So I have installed the latest package to my local app (app and libraries/repos are all local for all intents and purposes, but I am publishing them to NPM to circumvent the lack of linking working with VSCode and pnpm). Sidenote: I tried using pnpm link -global inside foo, and pnpm link -global inside bar, but it doesn't work, maybe the same problem I am facing here? ![]() Not exactly sure that it works this way, but from my small testing it seems like, vscode fully launches the interface and AFTER that start to load in the extensions. I publish a new version of to NPM and install it with pnpm add (or whatever new version). I recently found out the command to launch vscode without extensions ('code -disable-extensions) and it was identical startup time even with 20+ extensions. foo, and I import it inside of application. In more detail, say I import something like import from which I published from local. ![]() Basically, it never picks up the changes to the package. Similarly, on the first test platform, we observed a startup time of 14.56.2 seconds for the DEB package. (If I added new stuff to the new package version). In is useful to note that there is also some variation in the startup time of the Vscode application installed from the distribution repo (19.15.4 seconds), caused mostly by background system activity. That is, VSCode throws errors that the package doesn't exist, or if it did exist in the past, that the exports I'm accessing don't exist, etc. And none of the combinations I've tried worked.Īlso, you can open terminal at a specific folder: Ĭhange env: ""Īnd even change terminal to your liking with have switched to pnpm from yarn/npm, and have been running into a repeatable problem every time I install a new version of a package: VSCode has to be fully restarted before it picks up the change. Like this bash -init-file <(echo "source ~/.bashrc source some_init_script.sh")īut I could not pass this string into - it needs to be split into array somehow. Outside of VSCode you can do without creating extra file.
0 Comments
Leave a Reply. |