Issues with `@sanity/ui` in v3 plugin resolved by switching from Yarn to NPM

I upgraded to the latest version of

@sanity/ui

in my v3 plugin and now the builds fail complaining about missing props to every single sanity UI component. It’s fixed by adding these two props to all of them 😅

I know you want V3 feedback on Github. But not sure if this is V3 or Sanity UI related

It happens in the plugin package itself, not the V3 studio

Then running it in the V3 studio after linking up I get the following errors:

Could not resolve "@reach/auto-id"

Could not resolve "react-popper"

All imported by Sanity UI lib.

All have the following info after:

Hello! Can you try updating

@types/react

in your plugin?

Thanks, tried it but it didn’t work 😕

Hello I just stumbled over this message here, are you still experiencing this issue?

Hey thanks for checking. I managed to get this working again

What did you do (so when people have the same issue, they can find an answer here 🙂 )

Oh, haha, honestly I don't know. I left it for a few weeks, then tried again. Got different errors and resolved those instead 😅

#caption "programming" spongebob rainbow

hey this actually wasn’t fixed. The builds stopped failing, but vscode keeps complaining with red squiggly lines on Flex and Box from Sanity UI.

Hadn’t opened the custom input component I built in a while so I didn’t notice until today when I had to dig in there again for a different issue (I’m using the same custom input component on 2 different fields in the same doc but only one gets updated, even when I click the other one)

It might just be a TS issue with sanity/ui, could you try to update the package?

I upgraded sanity/ui but the issue is still there

adding the props removes the warning

latest version of TS (4.9.4)

Just bumping this thread to say I’m also getting this issue in a Sanity project I’m working on.

I still haven’t solved it either

Actually - I think I may have a fix. Just on a whim, I switched my package management on the project I’m in from Yarn 1.22 to NPM 8.19.3. Knocked out my node_modules and did a full reinstall. Seemingly solved at the moment.

right, so it’s a yarn issue. I’m working on a local plugin that’s currently linked with yalc/yarn link. Would need to update that first to test this out. We’re also using yarn for everything else. So would definitely prefer that it works for both yarn and npm. it looks like Andy found the cause