You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a somewhat recent release of TypeScript (I believe in some version around 5.2 but not sure) the rules for module/moduleResolution were tightened up. This causes DI-compiler to fail a build (pnpm build) with an error that module must be nodenext when moduleResolution is nodenext when using a fresh install of DI-compiler (latest TypeScript). The root cause is in @wessberg/ts-config where the following is set:
A workaround that resolves this build issue for just DI-compiler (though perhaps this is best resolved with some change to @wessberg/di-config) is to edit tsconfig.build.json and add moduleResolution: "node" to the compilerOptions:
In a somewhat recent release of TypeScript (I believe in some version around 5.2 but not sure) the rules for module/moduleResolution were tightened up. This causes
DI-compiler
to fail a build (pnpm build
) with an error thatmodule
must benodenext
whenmoduleResolution
isnodenext
when using a fresh install ofDI-compiler
(latest TypeScript). The root cause is in@wessberg/ts-config
where the following is set:A workaround that resolves this build issue for just
DI-compiler
(though perhaps this is best resolved with some change to@wessberg/di-config
) is to edittsconfig.build.json
and addmoduleResolution: "node"
to thecompilerOptions
:The text was updated successfully, but these errors were encountered: