Skip to content

finger-printing assets in production builds #40

Description

@mattmarcum

I noticed that when I do a production build my web-workers/*.js get fingerprinted...however the worker service isn't aware that the worker filenames are changed so we get a 404. I fixed it by adding a fingerprint: { exclude: ['web-workers']} to my ember-cli-build.js, but I think it might be good to support fingerprinting of the worker js files. Any ideas?

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions