
@sapphire/* because otherwise TS cannot properly resolve module augmentations. I forgot the exact option but it's one of the hoist pattern options. node16 for both module and moduleResolution then either use "type": "commonjs" or "type": "module" in your package.json based on whether you respectively want a CJS or ESM runtime. tsc / tsc-watch / tsup."type": "module" in your package.json) which causes the error of exports not being defined in an ES module (ESM) scope. So either change your compilation to ESM, or change "type": "module" to "type": "commonjs.