I'm not sure webpack or ionic fully support ES6 yet. May I ask why you need to run your app with ES6?

Ionic support ES6. My applications on Ionic are compiled under ES6, except for the use of TypeORM. Applications under the ES6 are much easier to debug if you use async/await. And, as far as I can see, they work a little faster, the interface is more responsive.

TypeOrm generally supports the ES6?

TypeORM should support ES6 but the compiled version in the package uses ES5. I haven't tried running the app or TypeORM with ES6

TypeOrm generally supports the ES6?

Of course typeorm supports es6.

TypeORM should support ES6 but the compiled version in the package uses ES5.

that should be zero issues with it compiled into es5 since es6 includes all features which present in the es5, right.

main.js: 7 Uncaught ReferenceError: Author is not defined

@extart create a demo repository for @daniel-lang and check the issue together since I dont have ionic stuff installed and not an expert in this area. Also provide a detailed error with code example, how do we know what is Author is not defined ? Where Author is not defined? Do you have circular relations?

@pleerock I can recreate the issue as @extart just tries to compile this example with es6. The error occures when trying to access the Author entity which, since it's es6, is a class.
I don't know, why this error occures as es6 classes are supported by all major browser...

If you run this example in Chrome (the command is "ionic serve"), then the same error occurs.

Do you have a working Ionic example (without TypeORM) that works with ES6 and that you can share?

I will prepare a working example and put a link here.

A working example is the standard Ionic example.
https://github.com/ionic-team/starters/tree/master/ionic-angular/official/super
Change to tsconfig.json "target": "es6" and run.
Everything works and if you look at the main.js, you can see the classes.
If you add TypeORM in this example, an error occurs.

@daniel-lang, Is there a chance to fix it?

@extart I finally had enough time to dive into this problem. It seems like it's exactly what @pleerock suspected in the beginning.

Do you have circular relations?

After removing the import statement from author.ts that loads post.ts the demo is compiled under es6. But this means, that the ManyToOne relation only works on one side. Checkout the es6 branch for the changes that I had to make and see with that works for you.

@daniel-lang Indeed, when I removed the circular relationship, it all worked. I checked in my project. In general, the problem is solved, but you probably need to somehow write about this feature in the documentation for TypeORM...
Thank you so much!

I would assume, that this is not a TypeORM specific problem but rather a problem of es6 with webpack. But it might be an issue to add it to the faq, @pleerock, that do you think?

@extart Can this issue be closed now?

@daniel-lang I think you can close this issue. Once again many thanks!

I have the same issue when I try to use typeorm in connection with vue / electron.
The solution to remove the ManyToOne decorator works but is not ideal.
Is there any chance this will be fixed in the near future?

The problem still exists. The manyToOne relationship is not working when compiled with webpack. I just can't remove the relationship.

Got it working when I have changed to

@Entity()
export default class User {} 

From

@Entity()
export class User {} 

Added "default" export in the entity

AND

imported like this

import User from './User';

Instead of
import {User} from './User';

There was a problem with webpack dealing with circular dependencies.