Please update class-transformer dependency to the latest version #783

slavafomin · 2021-10-08T15:19:46Z

Hello!

Thank you for this great library!

However, right now it requires [email protected] (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: [email protected]
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 [email protected]
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!

The text was updated successfully, but these errors were encountered:

slavafomin · 2021-10-08T15:22:19Z

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 · 2021-11-22T11:25:03Z

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 · 2021-12-09T07:46:35Z

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

Thanks!

juniopereirab · 2021-12-14T21:38:40Z

Same problem here...

TypeError: class transformer 1.classToPlain is not a function

RatakondalaArun · 2021-12-17T15:27:25Z

Is there any workaround for this?

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

amellalkamel · 2022-01-25T07:40:32Z

+1
this is a serious issue

ghost · 2022-03-14T13:57:49Z

Is there any update ?

seblaz · 2022-03-21T04:11:08Z

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

zSakuraEvilz · 2022-04-09T15:19:15Z

Is there no new update for this issue?

attilaorosz · 2022-04-09T21:11:06Z

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 · 2022-04-27T08:42:46Z

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.

saschajungfer · 2022-06-08T14:41:05Z

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:[email protected]
npm install class-transformer3@npm:[email protected]

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.

pfgallagher · 2022-06-08T17:36:03Z

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:[email protected]

npm install class-transformer3@npm:[email protected]

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.

@Killasushi - Could you please share your full package.json? Is there additional config you needed to do to point at the aliases? Doesn't seem to be doing the trick on my end.

saschajungfer · 2022-06-09T06:48:52Z

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:[email protected]

npm install class-transformer3@npm:[email protected]

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.
@Killasushi - Could you please share your full package.json? Is there additional config you needed to do to point at the aliases? Doesn't seem to be doing the trick on my end.

There is no additional config in my package.json. My package-lock.json looks like this, it is important that both versions do appear. That should be the case after running npm install class-validator12@npm:[email protected] (I'm using Node 16). Is that your case?

 "node_modules/class-validator": {
            "version": "0.13.2",
            "resolved": "https://registry.npmjs.org/class-validator/-/class-validator-0.13.2.tgz",
            "integrity": "sha512-yBUcQy07FPlGzUjoLuUfIOXzgynnQPPruyK1Ge2B74k9ROwnle1E+NxLWnUv5OLU8hA/qL5leAE9XnXq3byaBw==",
            "dependencies": {
                "libphonenumber-js": "^1.9.43",
                "validator": "^13.7.0"
            }
        },
        "node_modules/class-validator12": {
            "name": "class-validator",
            "version": "0.12.2",
            "resolved": "https://registry.npmjs.org/class-validator/-/class-validator-0.12.2.tgz",
            "integrity": "sha512-TDzPzp8BmpsbPhQpccB3jMUE/3pK0TyqamrK0kcx+ZeFytMA+O6q87JZZGObHHnoo9GM8vl/JppIyKWeEA/EVw==",
            "dependencies": {
                "@types/validator": "13.0.0",
                "google-libphonenumber": "^3.2.8",
                "tslib": ">=1.9.0",
                "validator": "13.0.0"
            }
        },

LucasGobatto · 2022-07-07T18:24:33Z

Still an issue

FrancisBehnen · 2022-07-11T10:08:21Z

If someone is forking, please let me know!

spicemc · 2022-07-14T16:25:14Z

I am using overrides in my package.json. This is my workaround:

...
  "overrides": {
    "class-transformer": "^0.5.1",
    "class-validator": "^0.13.2"
  },
  "dependencies": {
    "class-transformer": "^0.5.1",
    "class-validator": "^0.13.2",
...

Try with npm install --legacy-peer-deps to get it running.

JotaRaffalli · 2022-07-28T14:40:36Z

Pls, update this 😮‍💨

laujonat · 2022-07-30T10:15:29Z

No temporary workarounds?

spicemc · 2022-08-29T20:36:25Z

Did you try my suggested workaround?

Rasfuranku · 2022-10-31T01:07:52Z

Trying to install "routing-controllers": "^0.9.0" in a new project, having the same issue.

jstanislawczyk · 2022-11-14T15:02:50Z

Please update it. It's hard to use it in new project when it has such big issue

spicemc · 2022-11-14T19:35:40Z

If someone is forking, please let me know!

i forked it. Feel free to use it in your projects.

NoNameProvided · 2022-11-16T03:23:27Z

Hi folks! I have added branch protection bypass to @attilaorosz so he will be able to handle this.

FrancisBehnen · 2022-11-16T16:52:09Z

If someone is forking, please let me know!

i forked it. Feel free to use it in your projects.

Awesome, I've let the team know!

github-actions · 2022-12-27T00:21:24Z

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

slavafomin added flag: needs discussion Issues which needs discussion before implementation. type: feature Issues related to new features. labels Oct 8, 2021

gtpan77 mentioned this issue Jan 12, 2022

build(deps): bump class-transformer and class-validator version #827

Closed

6 tasks

FrancisBehnen mentioned this issue Jul 11, 2022

question: Is this project dead? #900

Closed

attilaorosz mentioned this issue Nov 23, 2022

chore: update class-validator and class-transformer #932

Merged

6 tasks

attilaorosz added status: has PR Issues which has a related PR closing the issue. and removed type: feature Issues related to new features. flag: needs discussion Issues which needs discussion before implementation. labels Nov 23, 2022

attilaorosz closed this as completed in #932 Nov 26, 2022

github-actions bot locked as resolved and limited conversation to collaborators Dec 27, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Please update class-transformer dependency to the latest version #783

Please update class-transformer dependency to the latest version #783

slavafomin commented Oct 8, 2021

slavafomin commented Oct 8, 2021

SandraShklyaeva commented Nov 22, 2021

biton-ron commented Dec 9, 2021 •

edited

Loading

juniopereirab commented Dec 14, 2021

RatakondalaArun commented Dec 17, 2021 •

edited

Loading

amellalkamel commented Jan 25, 2022

ghost commented Mar 14, 2022

seblaz commented Mar 21, 2022

zSakuraEvilz commented Apr 9, 2022

attilaorosz commented Apr 9, 2022

biton-ron commented Apr 27, 2022

saschajungfer commented Jun 8, 2022 •

edited

Loading

pfgallagher commented Jun 8, 2022

saschajungfer commented Jun 9, 2022

LucasGobatto commented Jul 7, 2022

FrancisBehnen commented Jul 11, 2022

spicemc commented Jul 14, 2022 •

edited

Loading

JotaRaffalli commented Jul 28, 2022

laujonat commented Jul 30, 2022

spicemc commented Aug 29, 2022

Rasfuranku commented Oct 31, 2022

jstanislawczyk commented Nov 14, 2022

spicemc commented Nov 14, 2022

NoNameProvided commented Nov 16, 2022

FrancisBehnen commented Nov 16, 2022

github-actions bot commented Dec 27, 2022

Please update class-transformer dependency to the latest version #783

Please update class-transformer dependency to the latest version #783

Comments

slavafomin commented Oct 8, 2021

slavafomin commented Oct 8, 2021

SandraShklyaeva commented Nov 22, 2021

biton-ron commented Dec 9, 2021 • edited Loading

juniopereirab commented Dec 14, 2021

RatakondalaArun commented Dec 17, 2021 • edited Loading

amellalkamel commented Jan 25, 2022

ghost commented Mar 14, 2022

seblaz commented Mar 21, 2022

zSakuraEvilz commented Apr 9, 2022

attilaorosz commented Apr 9, 2022

biton-ron commented Apr 27, 2022

saschajungfer commented Jun 8, 2022 • edited Loading

pfgallagher commented Jun 8, 2022

saschajungfer commented Jun 9, 2022

LucasGobatto commented Jul 7, 2022

FrancisBehnen commented Jul 11, 2022

spicemc commented Jul 14, 2022 • edited Loading

JotaRaffalli commented Jul 28, 2022

laujonat commented Jul 30, 2022

spicemc commented Aug 29, 2022

Rasfuranku commented Oct 31, 2022

jstanislawczyk commented Nov 14, 2022

spicemc commented Nov 14, 2022

NoNameProvided commented Nov 16, 2022

FrancisBehnen commented Nov 16, 2022

github-actions bot commented Dec 27, 2022

biton-ron commented Dec 9, 2021 •

edited

Loading

RatakondalaArun commented Dec 17, 2021 •

edited

Loading

saschajungfer commented Jun 8, 2022 •

edited

Loading

spicemc commented Jul 14, 2022 •

edited

Loading