Michael "Mike" Ferris
Michael "Mike" Ferris
Yeah, but "NodeNext" is a valid option even in commonjs I'm currently undergoing the migration to ESM on my main project and I'm doing small iterations toward ESM and transitioning...
I had a similar issue when trying to import a file not defined in the package.json exports definition https://github.com/MaintainX/yarn-plugin-workspace-lockfile/blob/8ae38c8799320b043f0db5cd1be3d81048711564/src/index.ts#L1-L14 ```ts // InstallOptions is not exported from `@yarnpkg/core` so just go...
Can you please revert this update? The repo is no where near ready for eslint 9 Even the CI throws this error, although that error was ignored 
Same experience as @itsjgf **Tracer version(s)**: 5.72.0 **Node.js**: 22.20 Affected service: our GraphQL API (Apollo Server). Other services are not noticeably impacted. We rolled back only dd-trace to version 5.67...
We are using `@apollo/server` 4.12.2
:+1: I've just hit that exact same problem. I was scratching my head on why the restore couldn't find the cache. In my case I was trying to change the...