Jiby Jose
Jiby Jose
have used inversify with swc and it works fine for me
@patak-dev curious what is the status of this PR, as I see this is the last issue blocking 3.2.
@bluwy sure, happy to help. I opened a new PR with the updated changes #10336
@bradzacher wouldn't it be possible to add type-information to the rule in a non breaking way, preferably using an option ? Such that the breaking behaviour only happens in case...
@bradzacher completely makes sense, was not aware of the complexity involved. For me personally your preferred solution perfectly gets the job done. Thanks for the explanation 👍
@sun0day I can confirm that in my case the problem happens here. its a monorepo, the tests are running inside `lambda-logger` package, and the `reflect-metadata` is hoisted to root `node_modules`...
@ChpShy I would consider that as a hack rather than a solution, as even though it would solve the resolution, it would also cause vitest to include all tests from...
@patak-dev I recently hit a similar issue, where I had a third party library which could have been completely tree shaken out but was not. And enabling dep optimiser manually...
@kresli please share your configuration, I had to manually enable dependency optimisation to get tree shaking in lib mode ```js { optimizeDeps: { disabled: false }, build: { commonjsOptions: {...