Lionel Tzatzkin

Hi @Joaroise, thanks for open the _Issue_. Can you please provide the `@reactour/tour` are you using? The portal exported from `/utils` was the source of some packages versions and build...

thank you @Allyson-Santana to share your (re)solutio! updating into `v3.1.4` you still need the `resolution` workaround?

Hi @MatheusWentzel, thanks for open the _Issue_. Mind creating a minimal reproduction in a sandbox in order to allow others to debug your use-case and try to find a solution?...

Thank you @schvenk for pointing this out. There are some problems with `@reactour/utils` packages build and publishing which is creating all this related errors. Can you share the `npm` override...

@schvenk mind testing again with a clean install (`rm -rf node_modules yarn.lock package-lock.json`? Thanks!

Thanks a lot for sharing the _overrides_, allowing others in the same situation to solve them also! In another thread (related on this mess) someone shared a solution just [updating...

> Locking sub-packages: is it not enough just to specific specific versions in each of your package.json files? Will investigate on how to do only on specific versions of `@reactour/tour`,...

@cjhensen can you try installing `@reactour/popover` as a dependency?

Closing as this issue is related on [this one](https://github.com/vercel/next.js/issues/12079)

[RFC](https://github.com/vercel/next.js/discussions/27953)