-
Notifications
You must be signed in to change notification settings - Fork 98
Importing issue #19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Sorry, I'm kinda swamped today. I will look into this tomorrow. So, if I understand well (otherwise correct me):
Thanks again, your help is much appreciated ! |
You are correct in all 3 points, with the little extra to say that beta 22 didn't adopt AOT but made it default (on purpose or not) angular/angular-cli#3368. Still I think it is important to generally be AOT compliant and also angular-cli complient, since I thing/guess the cli will be the future default boilerplate for angular2 apps and AOT because I'd rater decline this library then AOT since it gave me a extreme performance boost on one of my apps (Loading time form 10sec to 2sec, with no other changes then just compiling using AOT) |
I believe this issue is solved, could you double-check and close it ? |
Sorry I was on the road for a few days, so I couldn't test. I saw you merged everything so I tried importing version 0.4.1 from npm and tried running it with aot, but the map stayed blank. I don't know exactly what the problem now is, but I'll have a look and let you know. In the mean while could you please tell me exactly what procedure you run in order to publish on npm. |
I'm using the |
Do you have to run |
Hey!
|
Closing as angular2-openlayers is now AOT compliant. |
I'm using angular-cli for my project and never had a problem importing this library:
but since angular-cli beta 22 it no longer works. I get the following error:
I don't know exactly if this is a problem with angular-cli or with this library, so please have a look at it or let me know if you have no time/idea, then I'll create a issue at the angular-cli repo.
The text was updated successfully, but these errors were encountered: