Skip to content

update to rc.5 #843

Closed
Closed

Description

@PatrickJS

merge changes from https://github.com/AngularClass/angular2-seed

Angular 2 Seed will be the simple version of this repo. Both will be updated to Webpack 2

Activity

  1. self-assigned this
    on Aug 9, 2016
  2. aminebizid commented on Aug 9, 2016

    @aminebizid

    Great!

  3. PatrickJS commented on Aug 9, 2016

    @PatrickJS
    OwnerAuthor

    I have a simple version of the starter here https://github.com/AngularClass/angular2-seed that's updated to rc.5 it's where I experiment for changes in this repo

  4. shahmirn commented on Aug 10, 2016

    @shahmirn

    I tried to use RC5 and ran into an issue with uri.match is not a function, which is caused by _split being called on moduleId by angular, which in the case of webpack is a number.

    angular/angular#10595 is a PR created by @mhamel06 to fix the issue.

  5. PatrickJS commented on Aug 10, 2016

    @PatrickJS
    OwnerAuthor

    don't use moduleId in webpack

  6. shahmirn commented on Aug 10, 2016

    @shahmirn

    How about dependencies being used in the project that are using moduleId that we have no control over?

  7. PatrickJS commented on Aug 10, 2016

    @PatrickJS
    OwnerAuthor

    @shahmirn are they public deps on github? if so can you give me a link to the repo. You would use a loader to rewrite it and remove the moduleId but I need to create it.

  8. mhamel06 commented on Aug 10, 2016

    @mhamel06

    sorry not at computer now but I think my issue may have been from the material repo, since I still had the issue after removing my moduleIDs. this is with the latest Ng module version. https://github.com/angular/material2/blob/master/src/components/sidenav/sidenav.ts

    I think ensuring that the _split function is only called with the expected type should fix the core issue.

  9. houko commented on Aug 10, 2016

    @houko

    when rc5 will be updated in this project? @gdi2290 thank you

  10. snird commented on Aug 11, 2016

    @snird

    @gdi2290 the seed repo uses webpack 2, is it planned to update this starter repo to webpak 2 as well?

  11. PatrickJS commented on Aug 11, 2016

    @PatrickJS
    OwnerAuthor

    yup this repo will be updated to webpack2 and rc5

  12. DzmitryShylovich commented on Aug 11, 2016

    @DzmitryShylovich

    eta?

  13. paralin commented on Aug 11, 2016

    @paralin

    Looking forward to this, if you'd like me or the 100 other people here waiting for this to help, let us know how!

    I noticed when trying to update my own project that the hot loading stuff might be a bit ?? with rc5. Because you have to declare all of the components in a single place. Are we going to make multiple modules for a project, maybe? Seems really a lot more complicated than before.

  14. yyyyyyuanfei commented on Aug 12, 2016

    @yyyyyyuanfei

    Agree with @paralin , I also concern that if we're putting all the deps in one place, isn't it break the encapsulation of each component as they might depend on other libs that are not imported.

  15. 46 remaining items

  16. mac-bhaird commented on Aug 23, 2016

    @mac-bhaird

    Awesome!

    In the process of updating myself. Ran into the following,

    Can't bind to '<attribute>' since it isn't a known property of '<component>'.

    The same challenge is referenced in this issue: angular/angular-cli#1644

  17. dherges commented on Aug 23, 2016

    @dherges
    Contributor

    @qq83387856 can you share some code? maybe a diff what you've changed?

  18. mac-bhaird commented on Aug 23, 2016

    @mac-bhaird

    hmr was fixed in the recent update just by changing the angular router dependency (the only bit I pulled in so far)

  19. PatrickJS commented on Aug 25, 2016

    @PatrickJS
    OwnerAuthor

    alright webpack2, async, hmr are all working now

  20. fxck commented on Aug 25, 2016

    @fxck

    Great. What's next now @gdi2290? I wonder whether I should wait for that DLL stuff before I start refactoring everything..

  21. PatrickJS commented on Aug 25, 2016

    @PatrickJS
    OwnerAuthor

    DLLs will take some time since I have to deconstruct the config folder and move all of the comments into the type definition file

  22. shlomiassaf commented on Aug 26, 2016

    @shlomiassaf
    Contributor

    @gdi2290 great advanced work!

    I wonder if DLL's can be later on used for lazy routes/modules.
    In big apps it might be useful.

  23. PatrickJS commented on Aug 26, 2016

    @PatrickJS
    OwnerAuthor

    async load DLLs? ya, it's possible

  24. fxck commented on Aug 26, 2016

    @fxck

    I tried merging DLL myself. Failed miserably, there are countless typescript errors just by changing configs from js to ts.

    Should the config folder be part of exclude in tsconfig or something?

    When it's not in exclude, it's complaining about constants being re-declared, even when I'm not requireing the other files those constants are declared at. When it is in exclude, it cannot find require etc..

  25. PatrickJS commented on Aug 26, 2016

    @PatrickJS
    OwnerAuthor

    ya exclude the config folder

  26. fxck commented on Aug 26, 2016

    @fxck

    What do I do with Cannot find name 'require'. etc. then though? Use imports instead?

  27. yyyyyyuanfei commented on Aug 29, 2016

    @yyyyyyuanfei

    Any plan for the migration guide?

  28. fxck commented on Sep 1, 2016

    @fxck

    @gdi2290 any update on those dlls? :)

  29. jshamley commented on Sep 7, 2016

    @jshamley

    I had some similar errors and had to remove my typings folder from app root. Hope that helps someone else.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions