Project unhappy inside monorepo - suspect tsconfig issues, but not sure what I'm doing. | TypeScript Community | Page 1

novel holly Sep 27, 2024, 5:11 PM

#

Off-hand it does look like the sort of thing that'd be a tsconfig sort of thing - my guess would be a version conflict between the sharp dependency and payload

jolly hinge Sep 27, 2024, 5:12 PM

#

That was one of my thoughts, but I'm not seeing it. After the pnpm install, it looks like the right version is in place.

#

apps/cms/node_modules/sharp/package.json has version 0.32.6 which is the requested version.

#

That said .. /node_modules/sharp/package.json (top level) has 0.33.5, which is newer. I do not know why.

#

Hm. Storybook and Next.js canary have it as optional dependencies in the pnpm-lock.yaml

jolly hinge Sep 27, 2024, 10:16 PM

#

I used sherif to bring everything in line, and ... no change.

jolly hinge Sep 28, 2024, 2:14 PM

#

Okay - I had a little play with the tsconfig. I can definintely effect the errors. Now to figure out what's right/wrong.

#

❯ tsc --showConfig
tsconfig.json:20:25 - error TS6046: Argument for '--moduleResolution' option must be: 'node', 'classic', 'node16', 'nodenext'.

20 "moduleResolution": "bundler",
~~~~~~~~~

novel holly Sep 28, 2024, 7:43 PM

#

@jolly hinge You may check what version of tsc you're dealing with - I feel like the bundler option for moduleResolution isn't particularly new

jolly hinge Sep 28, 2024, 8:38 PM

#

You're right. Node is new enough, React is new enough, Next is new enough. I haven't checked what version of TSC I have. That will be the next check when I get to the keyboard.

jolly hinge Sep 28, 2024, 11:24 PM

#

Hm. I have version 4.9.5

#

and everything in the project request 5.6.2.

#

I have a system tsc that's out of date?!

jolly hinge Sep 28, 2024, 11:41 PM

#

Okay -t hat was part of a global bun install, apparently. The project has 5.6.2.

#

I removed the global install.

#Project unhappy inside monorepo - suspect tsconfig issues, but not sure what I'm doing.