Skip to content

Add second hash step to DCE'd modules #13

Description

@divmain

Since module hash is defined before all modules are loaded and processed, we'll need to either:

  • Perform a second hash step on modified bundles, so that the hash is a correct reflection of the runtime behavior; or
  • Modify the order of how interlock defines hashes. This would mean processing all modules and, after they have all been processed, hash and require-replace for all modules at once.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions