frank tartan
I used the nest-cli to create a project and I'm using typeorm as the ORM. there's this kind of problem in typeorm that currently - can only be solved by setting the compilerOptions.declaration to **false **in the generated tsconfig.json file in nest.
Is it safe to set this to false? or are there any drawbacks to this or possible breaking changes? I'm only creating a backend API for this proprietary project.
jolly oasis
Curious, what problem? It should be okay, as you're not generating a library, but I've not heard of something where that's the fix
frank tartan
Curious, what problem? It should be okay, as you're not generating a library, bu...
I'm creating some kind of base/generic repository and also service. I'm getting this similar issue, kindly check:
any other ideas how to fix such? 😀
jolly oasis
Go figure that TypeO has some weird bug like that
frank tartan
hmmm yeah. should I just stick with setting declaration to false?
are there any drawbacks?
jolly oasis
It just means that you won't get d.ts files in your output. Technically I think it should be fine
frank tartan
I see. so in a nutshell, just confirming, there's nothing to worry about disabling it since I'm not creating a library, right? is that all?
jolly oasis
I believe that should be the case