Florian Hammerschmidt

I just got bitten by this again (and wasted more time than I'd like to admit) - can we expect it to be resolved soon?

@chriswilty have you seen https://github.com/reason-seoul/yarn-plugin-rescript/ ? I think it should be mentioned in the docs somewhere, it is still completely new though.

The problem here is, that it is not re-exported in [this file](https://github.com/mui-org/material-ui/blob/v4.12.3/packages/material-ui/src/index.js). They only fixed that in v5, unfortunately: https://github.com/mui-org/material-ui/pull/21869/files

In my mind the Problems tab should reflect all the problems that the compiler also shows, but maybe that is just me?

The repo is just a limited demonstration of this behaviour, I tried to keep it as simple as possible, maybe it was a bit too simple. At work we use...

Sorry, I [updated the repo](https://github.com/fhammerschmidt/rescript-vscode-problems-tab/commit/ac584b607cf10a8caefa5d6ced338d1cf06b6b6a) now to run from root, to better reflect what we are doing at work.

What does command mean in this context? Because with `rescript build -with-deps` in the workspace root, I get errors for all packages.

Before we have a fix, can you try https://github.com/reason-seoul/yarn-plugin-rescript and check if the extension works with that?

Ok, I guess the plugin is not compatible with Windows (or your setup). Alternatively: Can you set `nodeLinker` to `node-modules` in your `.yarnrc.yml`? See: https://yarnpkg.com/configuration/yarnrc#nodeLinker Then the extension should work...

Just to clarify: It does not make sense for the extension to support yarn PnP yet, when even the compiler does not: https://github.com/rescript-lang/rescript-compiler/issues/3276 As soon as you add some dependencies,...