typeorm: Cannot set property EntityManager of # which has only a getter

Issue type:

[x] bug report

Database system/driver:

[x] postgres

TypeORM version:

[x] latest

Steps to reproduce or a small repository showing the problem:

TypeError: Cannot set property EntityManager of #<Object> which has only a getter
    at Object.<anonymous> (/usr/src/app/node_modules/typeorm/index.js:120:23)
    at Module._compile (internal/modules/cjs/loader.js:1185:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1205:10)
    at Module.load (internal/modules/cjs/loader.js:1034:32)
    at Function.Module._load (internal/modules/cjs/loader.js:923:14)
    at Module.require (internal/modules/cjs/loader.js:1074:19)
    at require (internal/modules/cjs/helpers.js:72:18)
    at Object.<anonymous> (/usr/src/app/lib/index.js:5:19)
    at Module._compile (internal/modules/cjs/loader.js:1185:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1205:10)

Somehow getting this random error now and have. Literally tried rolling back my code and everything. Any suggestions where to look?

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Reactions: 112
  • Comments: 40 (1 by maintainers)

Commits related to this issue

Most upvoted comments

Edit your package.json at your project root directory to avoid using latest version of tslib

  "resolutions": {
    "tslib": "1.11.2"
  }
+43
possible819 on May 13, 2020

Temporary workaround: npm i tslib@1.11.2 --save and remove ^ before the version in package.json:

...
"tslib": "1.11.2",
...
+26
IncoCode on May 12, 2020

tslib updated which is exposing a pre-existing issue with double-exporting symbols:

TSLib behavior change and other folks having problems with it have been reported there:

+20
mgabeler-lee-6rs on May 12, 2020

@possible819 you’ve saved my time.

+6
lotstar87 on May 13, 2020

Still diagnosing but in case this helps someone, it appears that even locking to tslib@1.11.2, a clean yarn install will still manifest this error. However a clean npm install will allow my app to run fine. Very odd.

+6
eddieajau on May 12, 2020

I have the same problem. This is fantastic!

+4
alexey-nobody on May 12, 2020

Okay, I fixed it and with yarn!!! After adding tslib@1.11.2, I checked the version and the syntax to be correct in the package.json file. Then, as it is stated above I also added, at the end of the package.json file, this:

...
  "resolutions": {
    "tslib": "1.11.2"
  }
...

Important: If you install tslib@1.11.2 with npm, make sure to remove the package-lock.json file. For some reason, it also asked my to re-install reflect-metadata.

Finally, I fixed it and everything works correctly right now! Thank you for the support guys.

+3
georgekrax on May 13, 2020

Lo que hice fue regresar a mi versión de typeorm a la versión 0.2.4. El problema se fue enseguida.

sí, el mío también, pero ¿tuvo alguna otra solución que funcione con la última versión de typeorm?

Nada amigo, por el momento esa es la unica solución que he podido encontrar.

+1
degoprisss on Apr 13, 2022

Lo que hice fue regresar mi versión de typeorm a la version 0.2.4. El problema se fue enseguida.

+1
degoprisss on Apr 8, 2022
Read more comments on GitHub
← typeorm: Cannot read property 'name' of undefined
typeorm: Cannot update entity because entity id is not set in the entity. →