Please update class-transformer dependency to the latest version

[slavafomin]

Hello!

Thank you for this great library!

However, right now it requires class-transformer@0.3.1 (exact version 0.3.1) as a peer dependency. This prevents my project from using the latest version of the class-transformer (which is 0.4.0).

This generates the following error on npm install:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: @acme/project
npm ERR! Found: class-transformer@0.4.0
npm ERR! node_modules/class-transformer
npm ERR!   class-transformer@"0.4.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer class-transformer@"^0.3.1" from routing-controllers@0.9.0
npm ERR! node_modules/routing-controllers
npm ERR!   routing-controllers@"0.9.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

Would you be so kind to update class-transformer dependency to the latest version?

Thanks!

[slavafomin]

The same issue is with class-validator.

Also, it would be much easy to avoid these kind of issues if you would switch to a stable semver range (major version > 0) because it would allow to match dependencies in a more relaxed manner.

[SandraShklyaeva]

Dependency update sounds even more urgent because of the latest security vulnerability fixes for the following packages:
class-validator => 0.13.2 (changelog)
class-transformer => 0.5.0 (changelog)

[biton-ron]

Same issue for us, a fix will be a great help.

Thanks!

[juniopereirab]

Same problem here...

TypeError: class transformer 1.classToPlain is not a function

[RatakondalaArun]

Is there any workaround for this?

I want to use exposeDefaultValues which was added in v0.3.2

[amellalkamel]

+1
this is a serious issue

Is there any update ?

[seblaz]

Hi @NoNameProvided @attilaorosz, would you mind having a look at the pr? Thanks!

[zSakuraEvilz]

Is there no new update for this issue?

[attilaorosz]

Seems like there are no real breaking changes in terms of class-transformer usage (I might be wrong here) so you can just update the package since it is only a peer dependency.

[biton-ron]

Seems like there are no real breaking changes in terms of class-transformer usage (I might be wrong here) so you can just update the package since it is only a peer dependency.

We're working with TypeScript and we get some type differences that reflect breaking changes in the library.

[saschajunius]

Is there any workaround for this?

I want to use exposeDefaultValues which was added in v0.3.2

I just found a workaround which seems to work, you can install two versions of the same package using an alias:

• npm install class-validator12@npm:class-validator@0.12.2
• npm install class-transformer3@npm:class-transformer@0.3.1

My package.json now looks like this:

        "class-transformer": "^0.5.1",
        "class-transformer3": "npm:class-transformer@^0.3.1",
        "class-validator": "^0.13.2",
        "class-validator12": "npm:class-validator@^0.12.2",

Never saw that syntax before, but this is working for me.