Anders Evenrud

I immediately updated now that I saw #2438 was merged. This seems to have solved all of the issues I had relating to this (and so much more) :heart_eyes:

I've been running main and stock settings for a few days now (and did an update last night). Unless my problems lies elsewhere then I don't think this issue has...

@cseickel > Have you checked the process stats when this happens, is it using a lot of memory or cpu? I noticed that memory usage was at around 7G for...

Okay, it just happened again. Memory usage started climbing and when I hit around 7G as before things started to lag like crazy. Watched it go all the way up...

@cseickel I followed your comment above, and in my first round I enabled diagnostics. And that definitively has something to do with it. A very easy way to reproduce this...

@cseickel Yeah, after a bit more testing this does indeed seem to be a general issue. On my desktop it's not really an issue (with `diagnostics` etc disabled), but my...

@cseickel > but in the meantime can you tell me if you are running nightlies? If you are, can you try using a stable version of neovim and telling me...

The easiest way to do this is to use the externals feature of Webpack: https://webpack.js.org/configuration/externals/ and load react via a CDN using script tags either via webpack or the dist...

> via a CDN using script tags This can also be loaded locally also of course. I believe the webpack resolver is smart enough to only load these once as...

@hello-smile6 The issue is not about npm packages on the filesystem, but how they end up in a compiled bundle, which is Webpack related.