Skip to content

71% sealing ... #8126

Closed
Closed

Description

@elvisbegovic

Bug Report or Feature Request (mark with an x)

- [x ] bug report -> please search issues before submitting

Versions.

@angular/cli: 1.4.9
node: 6.11.0
os: win32 x64
@angular/*: 4.4.6
@angular/cli: 1.4.9
typescript: 2.3.4

Repro steps.

udpate from 1.4.6 to 1.4.9 then run ng s --sm=false

The log given by the failure.

blockin 71% sealing 1mn then go ahead

here's gif :
71

And how I hide all theses modules in console I juste want filename as before this polluate my console very ugly.

image

Activity

  1. royibernthal commented on Oct 22, 2017

    @royibernthal

    I'm experiencing the same issue, in my case it can be stuck on sealing for 5-10 min before it moves on.

  2. liuxinqiang commented on Oct 23, 2017

    @liuxinqiang

    Same problem...

  3. mtekkie commented on Oct 23, 2017

    @mtekkie

    I have the same problem.

  4. bingzheyuan commented on Oct 24, 2017

    @bingzheyuan

    I have same issue, could you check webpack version? The issue shows up starting from webpack@^3.7. For webpack 3.6, sealing takes only seconds.

  5. nashmaniac commented on Oct 24, 2017

    @nashmaniac

    @bingzheyuan I checked that.. @angular/cli@1.4.9 uses webpack@3.7.1

  6. kkudryaev commented on Oct 24, 2017

    @kkudryaev

    I also have the same issue and almost are very sure that the problem is with the Webpack. Downgrade to @angular/cli@1.4.6 helped.

  7. self-assigned this
    on Oct 25, 2017
  8. added
    P1Impacts a large percentage of users; if a workaround exists it is partial or overly painful
    on Oct 25, 2017
  9. filipesilva commented on Oct 25, 2017

    @filipesilva
    Contributor

    This does sound like a problem in the new webpack versions. We updated to 3.7.1 in #8014 and 3.8.1 in #8132.

    3.8.1 might fix this, but it wasn't released in 1.4.9. It should be in 1.5.0 final that is coming out very soon, and you can also try out 1.5.0-rc.3 meanwhile.

  10. kkudryaev commented on Oct 25, 2017

    @kkudryaev

    Thanks. It works on 1.5.0-rc.3 and node 6.11.0.

  11. nashmaniac commented on Oct 26, 2017

    @nashmaniac

    yes. it works a lot faster than the previous.

  12. elvisbegovic commented on Oct 26, 2017

    @elvisbegovic
    ContributorAuthor

    works faster only for this 71% step not faster globally , be clear

  13. nashmaniac commented on Oct 27, 2017

    @nashmaniac

    yes. lastly my build would take about 11.5 mins now it's taking 2.5 mins. lot improved on that perspective. but it's not fast like the earlier versions.

  14. elvisbegovic commented on Oct 27, 2017

    @elvisbegovic
    ContributorAuthor

    I confirm in v1.5.0-rc.3 it doesn't block a lot on 71%, now I have little blocking at step
    76% basic chunk optimization donno whats done here...

    here you are:
    rld

    this is without aot of course

  15. elvisbegovic commented on Oct 30, 2017

    @elvisbegovic
    ContributorAuthor

    is this fixed in rc6 because there is not block at 71% but only at
    0% compiling more than 30seconds
    and semestimes on
    10% building modules 0/1 modules 1 active ...s\i10\src\app\app.module.ngfactory.js more than 30seconds

    it depend one or other

    (in new project it's very fast)

  16. nashmaniac commented on Oct 30, 2017

    @nashmaniac

    @istiti facing this 10% building modules wait.. here too.

  17. filipesilva commented on Nov 4, 2017

    @filipesilva
    Contributor

    I think 1.5,0 final addressed the issue discussed here so I'm closing this issue.

  18. angular-automatic-lock-bot commented on Sep 7, 2019

    @angular-automatic-lock-bot

    This issue has been automatically locked due to inactivity.
    Please file a new issue if you are encountering a similar or related problem.

    Read more about our automatic conversation locking policy.

    This action has been performed automatically by a bot.

  19. locked and limited conversation to collaborators on Sep 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P1Impacts a large percentage of users; if a workaround exists it is partial or overly painfultype: bug/fix

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions