Skip to content
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

updated deps & readme, cleaned up scripts #1367

Merged
merged 1 commit into from
Jan 12, 2017

Conversation

colinskow
Copy link
Contributor

@colinskow colinskow commented Jan 12, 2017

  • Updated dependencies
  • Cleaned up NPM scripts, removed redundant & deprecated ones
  • Fixed e2e:live
  • Updated README with info on DLLs, external stylesheets, and updated scripts
  • Travis script also tests dev/dll build
  • Added delay in Travis script to reduce likelihood of failure

Resolves #1353

@colinskow
Copy link
Contributor Author

Protractor ^5.0.0 dropped support Node 5. If we want to update Protractor further we will need to drop support for Node 5. In my opinion we should support only Node lastest and Node LTS.

@@ -142,10 +141,10 @@
"ts-node": "^2.0.0",
"tslint": "~4.3.1",
"typedoc": "^0.5.3",
"typescript": "2.0.10",
"typescript": "~2.1.5",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unless Angular has changed their stance on this and resolved the AOT issues, this should not be changed as last I checked it isn't officially supported until Angular 4.x

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In Angular 2.3.x with TS 2.1.x the NGC compiler left the compiled directory mostly empty and didn't generate the ngfactory files. Now with Angular 2.4.3 our AoT build works perfectly with TypeScript 2.1 and the tests are passing with flying colors.

While the issue technically hasn't been closed yet, the problem seems to have been fixed. My opinion is that it is safe to merge since the tests that failed before due to the issue are now passing.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Landed in 2.4.2

screen shot 2017-01-12 at 3 38 56 pm

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems that TS 2.1 is still not supported for AOT: angular/angular#13294

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pglazkov This is really interesting... I wonder why they say it's not working.

I did some crazy things with typescript nightly with no issues... AOT 100%

I wonder if it's ngc-webpack to "blame"

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm running TypeScirpt 2.1.5 in production on Angular 2.4.3 and I have no issues with AOT compilation in either of my largest apps.

Perhaps it would be more accurate to say that isn't flakey. The language service issue was the initial blocker to TypeScript 2.1 which is referenced above.

I do on the other hand compile my AOT with ngc directly which may support the ngc-webpack theory.

@joshwiens joshwiens merged commit a7a78f0 into PatrickJS:master Jan 12, 2017
@colinskow
Copy link
Contributor Author

@katallaxie you haven't submitted a pull request for i18n yet!
https://angular.io/docs/ts/latest/cookbook/i18n.html

awcodify pushed a commit to awcodify/d3-angular-4 that referenced this pull request Aug 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants