Error: no such file or directory ./bolt/packages/build-tools/node_modules/find-up about bolt HOT 8 CLOSED

Thanks @mralexho for reaching out! We are taking a look at this and can get back to you shortly.

-Margo
Bolt Design System Product Owner

from bolt.

Hey thanks @mralexho!

We've been running into this same error on our end as well (we already had a ticket on our internal board to debug this). We're still not quite sure why this is happening (possibly an issue with an upstream dependency) however in our experience, re-running yarn a 2nd time almost always seems to do the trick!

(also just in case it pops up for ya, there's also been this particular Sharp error more recently popping up when the images task is first booting up. Same workaround applies (re-running the build tools) but this has been a more finicky bug to squash!)

from bolt.

Thanks for the quick response!

@sghoweri you were correct, running the command a 2nd time fixes the issue (not sure why I didn't just try that before). Thanks for the heads up with sharp builds 🤞

from bolt.

I just ran the next command npm start (twice this time) and received the following -

Let me know if you need any additional debug logs. And thanks for helping!

from bolt.

Sorry I'm not too sure how to handle. I applied
@nstuyvesant's lovell/sharp#1593 (comment) steps for installing vips and sharp but now I'm getting these errors -

from bolt.

@mralexho ugh, so sorry for the rough onboarding!

Since @bolt/build-tools should be requiring address, I’m wondering if your version of yarn could be out of date or if the Sharp Mac OS workaround could have thrown something off with the install of the monorepo dependencies 🤔

Out of curiosity, could you try running npm run clean to wipe any local NPM / Composer dependencies, then try running npm run setup and npm start to see if that missing package gets correctly installed?

from bolt.

Hi @sghoweri, no apologies necessary at all! I'm sure you have many other things to do than debug issues.

I upgraded to yarn v1.16.0 and ran npm run clean and npm run setup but still have some dependency errors -

It looks like the same original error with the find-up module?

from bolt.

@sghoweri @margoromo just pulled the latest codebase and it's running now!

Can't wait to test this out with my team. Thanks! 😸

from bolt.