# BudError: @roots/bud-framework tried to access undefined

**URL:** https://discourse.roots.io/t/buderror-roots-bud-framework-tried-to-access-undefined/27745
**Category:** sage
**Tags:** bud
**Created:** 2024-07-08T06:40:02Z
**Posts:** 2

## Post 1 by @Suraj_Sanwal — 2024-07-08T06:40:02Z

I have a sage 10 setup working perfectly in ubuntu, I’m trying to make a clone of the same working setup in mac but getting the BudError when runs `yarn build` or `yarn dev`:

> @roots/bud-framework tried to access undefined, but it isn’t declared in its dependencies; this makes the require call ambiguous and  
> unsound

Also, I saw there are two files auto generating: `.pnp.cjs` and `.pnp.loader.mjs` and there is no node\_modules folder ever after running `yarn install`

Can anyone suggest the possible solution to encounter this issue?

Using  
Sage: 10.7.0  
DevDependencies and versions:  
{  
“@roots/bud”: “^6.23.1”,  
“@roots/bud-babel”: “6.20.0”,  
“@roots/bud-framework”: “^6.23.1”,  
“@roots/bud-react”: “6.20.0”,  
“@roots/bud-tailwindcss”: “6.20.0”,  
“@roots/sage”: “6.20.0”  
},

---

## Post 2 by @alexstrand — 2024-07-08T13:05:59Z

Hi,

From Yarn docs:

> Remember that migrating to Yarn PnP is optional: you can revert to `node_modules` installs at any time by setting the `nodeLinker: node-modules` setting in your project’s `.yarnrc.yml` file.

> **[Plug'n'Play | Yarn](https://yarnpkg.com/features/pnp)**
>
> An overview of Plug'n'Play, a powerful and innovative installation strategy for Node.

Also, from my experience, it is best to use matching versions of all @roots packages, as you are using mixed version numbers.

Good luck,  
Alex