Skip to content

ng github-page:deploy not generating files with hashes, only main.bundle.js #4048

Closed

Description

@rxjs-space

Please provide us with the following information:

OS?

Windows10.

Versions.

Please run ng --version. If there's nothing outputted, please run in a Terminal: node --version and paste the result here:
angular-cli: local (v1.0.0-beta.25.5, branch: master)
node: 6.5.0
os: win32 x64
@angular/common: 2.4.3
@angular/compiler: 2.4.3
@angular/core: 2.4.3
@angular/forms: 2.4.3
@angular/http: 2.4.3
@angular/platform-browser: 2.4.3
@angular/platform-browser-dynamic: 2.4.3
@angular/router: 3.4.3
@angular/compiler-cli: 2.4.3

Repro steps.

Was this an app that wasn't created using the CLI? What change did you do on your code? etc.
My app created using ng new.

The log given by the failure.

Normally this include a stack trace and some more information.
No error.

Mention any other details that might be useful.

I can have main.addad3558a8e7df8de84.bundle.js with ng build --prod, but only main.bundle.js with ng github-paged:deploy. Even ng github-paged:deploy --prod won't give any hashes.
No such thing in v1.0.0-beta24.


Thanks! We'll be in touch soon.

Activity

  1. rxjs-space commented on Jan 16, 2017

    @rxjs-space
    Author

    I added outputHashing: 'bundles' after this line , and there I have the hashes. I think hashes should be default behavior for github-pages:deploy, since it's using prod mode.

  2. filipesilva commented on Jan 16, 2017

    @filipesilva
    Contributor

    This is a bug. With the introduction of #3885, the deploy command (and test) weren't updated to also generate/verify the hashes.

  3. added
    P1Impacts a large percentage of users; if a workaround exists it is partial or overly painful
    on Jan 16, 2017
  4. self-assigned this
    on Jan 16, 2017
  5. filipesilva commented on Feb 3, 2017

    @filipesilva
    Contributor

    Closed via #4385.

  6. angular-automatic-lock-bot commented on Sep 6, 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.

  7. locked and limited conversation to collaborators on Sep 6, 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