Module not found StringUtils

[XerxesAkaEnno]

Issue Description

After updating to version 0.2.42 I get an error on my next js application which says "Module not Found ../typeorm/util/StringUtils"
Seems like its no exported any more.

Expected Behavior

The StringUtils should be exported, for minor version.

Actual Behavior

  StringUtils are not exported to implement as module

Steps to Reproduce

For example load up a Next JS Project with Next-Auth which has Typeorm as dependency.  

My Environment

Dependency	Version
Operating System
Node.js version	x.y.zzz
Typescript version	x.y.zzz
TypeORM version	x.y.zzz

Additional Context

Relevant Database Driver(s)

DB Type	Reproducible
aurora-data-api	no
aurora-data-api-pg	no
better-sqlite3	no
cockroachdb	no
cordova	no
expo	no
mongodb	no
mysql	no
nativescript	no
oracle	no
postgres	no
react-native	no
sap	no
sqlite	no
sqlite-abstract	no
sqljs	no
sqlserver	no

Are you willing to resolve this issue by submitting a Pull Request?

• ✖️Yes, I have the time, and I know how to start.
• ✖️ Yes, I have the time, but I don't know how to start. I would need guidance.
• ✖️ No, I don’t have the time, but I can support (using donations) development.
• ✅ No, I don’t have the time and I’m okay to wait for the community / maintainers to resolve this issue.

[visarya]

facing the same issue

[XerxesAkaEnno]

@visarya
As a workaround for projects or dependencies following works:

This workaround works on my pipeline.

Project Step:

1. Add to the package.json following: "typeorm": "^0.2.42",
   The package wouldn't be downloaded again because an dependency already had it.

Pipeline Steps/Local Steps
2. run npm install

3. run npm remove typeorm

4. run npm install typeorm@0.2.41

[anuragteapot]

facing the same issue. Even i was on old version ^0.2.25. My deployments are failing suddenly

[spalt08]

Related:

tonivj5/typeorm-naming-strategies#16

[pleerock]

we can export StringUtils, it's not an issue. But the question is what change bring this error. I bet it's something related to new ESM support. @giladgd do you have any ideas if your PR #8536 could introduce this kind of issue?

[anuragteapot]

I am wondering how its affecting older versions ? ^0.2.25

[pleerock]

I am wondering how its affecting older versions ? ^0.2.25

it doesn't affect old version, because of ^ it installs the latest right now on your machine.

[nallenscott]

Appears to be related to ESM:

[pleerock]

any hints on how to reproduce this issue at it's minimal (without other big dependencies like nestjs, etc)

[spalt08]

@pleerock Just use the typeorm-naming-strategies package (snake case strategy for example) in your connection config

[anuragteapot]

I am wondering how its affecting older versions ? ^0.2.25

it doesn't affect old version, because of ^ it installs the latest right now on your machine.

Yes minor version issue.

[giladgd]

@pleerock I managed to reproduce the issue and fix it.
I've opened #8660 to fix this issue

[pleerock]

@giladgd thanks for urgent response, fix was released in 0.2.43.

[k-patton]

I am seeing this issue again in version 0.2.44

[giladgd]

@k-patton I tried to reproduce it but this problem didn't occur to me.
Could you please provide me with an example project where it happens to you?

[kenchoong]

I using typeorm 0.2.44

use it with Nx. Having the same issue as above.

and I still havent find out which part is possible going wrong

[nastari]

same problem.... sad

[Alvaro948]

Same issue with typeorm@0.2.45

[adamskrodzki]

In hope that this will help anybody.

In my case problem was fixed by using node v16.13.0 instead of v14.18.1

[eldpswp99]

I had this issue when using jest v28 with typeorm@0.2.45.

I fixed this problem by downgrading jest to 27.5.1